thats true on many systems... nothing special about 0x0 other than NULL happens to be defined as 0 in most toolchains an some functions use NULL to report an error.
The technical definition of opoerating system is the software that manages the resources of the computer, i.e. RAM, storage, processor time, etc (Typically known as the Kernel).
I was involved in a product with a large codebase structured like this and it was a maintainability nightmare with no upsides.
Multiple attempts were made to move away from this to no avail.
Consider that the code has terrible readability due to no syntax-sugar, the compiler cannot see through the pointers to optimise anything, tooling has no clue what to do with it.
On top of that, the syntax is odd and requires any newbies to effectively understand how a c++ compiler works under-the-hood to get anything out of it.
On top of those points, the dubious benefits of OOP make doing this a quick way to kill long-term maintainability of your project.
For the devs who come after you, dont try to turn C into a poor-mans C++.
If you really want to, please just use C++.
Correct me if I'm wrong but the next LTS will be 26.04 which would give them 6 months to get maturity and stability...
For such an important set of utilities, that seems unlikely.
The correct phrase is "mechanical sympathy" but it means effectively the same.
Its relatively well known in software optimisation and means tailoring the design of the software to match the characteristics of the hardware.
There are similar devices (i.e. SiLabs) that allow multi-protocol use with the radio (I would expect Nordic to have a similar feature set), tho yes, you're right the resource issue would be a major limitation.
static allocation is the recommended mechanism in embedded code for reliability reasons, you have thought about you worst-case allocation and accounted for it... right?
Also fragmentation and dynamic behaviour are bad things when your code has to run "forever".
packets are sequenced, integrity checked and encrypted to prevent replay attacks so unlikely to be a simple "send packet again" issue.
More likely a key debounce issue or driver issue.
- scaling vertically is cheaper to develop
- scaling horizontally gets you further.
What is correct for your situation depends on your human, financial and time resources.