4 ms·
>you probably have them in your head as coding guidelines anyway Ha, if only. Sure, if everyone working on the project is a skilled C dev then yeah, but not wh
by FirmwareBurner 3y ago
>you probably have them in your head as coding guidelines anyway
Ha, if only. Sure, if everyone working on the project is a skilled C dev then yeah, but not when you're piecing together code form a bunch of bodyshops as it often happens in automotive where everything is contracted out to the lowest bidder to push costs down, so MISRA is there as a minimum common denominator to make sure that your code doesn't reach rock bottom in the process.
- einpoklum 3y agoOk, fair enough, I'm relatively skilled and I've taught C (and some C++) to people, so I guess I'm biased. On the other hand - extensive compiler warnings + non-MISRA general-purpose static analysis would probably cover those.