3 ms·
It's 15 pounds. Can someone give the gist of it?
by mgaunard 3y ago
It's 15 pounds.
Can someone give the gist of it?
- ska 3y agoIt’s a standard for the use of c++ in critical systems. Basically a guide to techniques and language features you can and can’t use (or how) and still have very predictable/controllable system behavior.
- 1MachineElf 3y agoI recently watched this webinar[0] about it, presented by the company ParaSoft, which develops a static analysis tool and compliance reporting solution for businesses required to use MISRA C++[1]. [0] https://www.brighttalk.com/webcast/18694/602198 https://www.brighttalk.com/webcast/18694/602198 [1] bhttps://www.parasoft.com/white-paper/buyers-guide-static-code-analysis-for-embedded-development/?gtd=false https://www.parasoft.com/white-paper/buyers-guide-static-cod...
- josefx 3y agoAt least the wiki article on MISRA C cites multiple studies that consider the rules mostly pointless, in some cases outright counterproductive and basically accuses it of being only beneficial to companies selling compliance tools. If MISCRA C++ is anywhere as bad you might be better of avoiding it.
- almostnormal 3y agoWith strict rules anyone can write software that does not instantly fail horribly (e.g., if pointers are not allowed, there won't be a bad dereference (but that's not even in misra)). That helps outsourcing to the lowest bidder.
- sam_bristow 3y agoYou can get a reasonable flavour of thw type of rules by looking at the Autosar C++ standard. MISRA C++ 2023 is a massive improvement over the previous (2008) version.