is that I previously blogged about it
blog.martincowen.me.uk/comment-driv...
Why not adopt this practice every day?
is that I previously blogged about it
blog.martincowen.me.uk/comment-driv...
Why not adopt this practice every day?
You can't avoid this by using __FILE__ etc in this function, or all calls will give the same values.
You can't avoid this by using __FILE__ etc in this function, or all calls will give the same values.
If you put the __FILE__ and __LINE__ macros in the called functions, it will not show you the caller function location. Need to use a macro which wraps the function and passed params on, & adds these macros.
🧵
If you put the __FILE__ and __LINE__ macros in the called functions, it will not show you the caller function location. Need to use a macro which wraps the function and passed params on, & adds these macros.
🧵
Ctrl-K Ctrl-S brings this up.
Ctrl-K Ctrl-S brings this up.
from to
from to
#electronics #firmware #STM32 #KiCad
#electronics #firmware #STM32 #KiCad
Before and after
Before and after
Second of 4 posts on the firmware for my PCB, covering designing FSMs, using DOT language, Graphviz and visualisers to autogenerate C code with a python script. Links to expert calcs on real-time scheduling.
#STM32 #firmware
Second of 4 posts on the firmware for my PCB, covering designing FSMs, using DOT language, Graphviz and visualisers to autogenerate C code with a python script. Links to expert calcs on real-time scheduling.
#STM32 #firmware