Overriding target_get_force_bootloader about dapboot HOT 4 OPEN

I've only been marking functions as weak as a convenience for some of hooks that have default / no-op implementations in dummy.c.

In general, to customize the behavior for a target, I would either add more #ifdef controlled code to target_stm32f103.c or create a new target directory if the changes are not broadly applicable or too extensive to put in the common implementation.

from dapboot.

Just in terms of extensibility without butchering the core code, I've been finding the weak functions really nice. It's meant that I can extend the code for a weird use case without junking up the core implementation and still keep the cut-and-paste duplication to a minimum.

from dapboot.

Weak functions work okay if there's only one level of overriding necessary, but IIRC, it's not defined what happens if you provide multiple weak definitions of a symbol to the linker. I agree that it is nice to be able to extend things without modification, but there are only so many hacks we can get away with before we end up building a poor version of C++.

from dapboot.

Understood.

from dapboot.