3 ms·

In addition to avoiding undefined behavior, MISRA discourages language features that are "dangerous" like I/O and dynamic memory routines. It also defines some

by hgs3 3y ago

In addition to avoiding undefined behavior, MISRA discourages language features that are "dangerous" like I/O and dynamic memory routines. It also defines some (controversial) styling rules, such as requiring functions to have exactly one exit point.

cordenr 3y ago
SE/SE is called out explicitly in the ISO26262 documents (functional safety in road vehicles). This makes it easy to defend the inclusion of such a guideline, even if you may not agree with it. But as it happens, MISRA C++:2023 doesn't have this guideline.
bfrog 3y ago
no_std rust then which has no i/o or heap, and what misra rules would there even need to be?
- hgs3 3y ago
  Code styling rules, such as requiring functions to have exactly one exit point, could be carried over to Rust. Many existing rules are still relevant for unsafe blocks and there would likely be new rules for panic.
  - bfrog 3y ago
    I believe the single exit rule was dropped