3 ms·
The rule you are referring to is a "required" (not a "mandatory") rule. You can deviate from it and still be MISRA-C compliant. People write deviations for all
by okl 8y ago
The rule you are referring to is a "required" (not a "mandatory") rule. You can deviate from it and still be MISRA-C compliant. People write deviations for all kinds of reasons. Here are some rationales for deviations:
https://lars-lab.jpl.nasa.gov/JPL_Coding_Standard_C.pdf https://lars-lab.jpl.nasa.gov/JPL_Coding_Standard_C.pdf (Rule 5 on page 10 on malloc)
https://www.keil.com/pack/doc/CMSIS/Core/html/coreMISRA_Exceptions_pg.html https://www.keil.com/pack/doc/CMSIS/Core/html/coreMISRA_Exce...
The unit of reuse that defines the type, example: http://c-faq.com/struct/sd1.html http://c-faq.com/struct/sd1.html
- CyberDildonics 8y agoSo your solution, in a thread about using a fixed amount of memory, is to do nothing different and let anything use the heap at any time because it might be possible in some cases to get it past MISRA standards? I'm not really sure of what you are trying to say, it seems you keep skewing further from the original discussion.