Critical embedded software should use static checking tools with a defined and appropriate set of rules, and should have zero warnings from those tools.Consequences:While rigorous peer reviews can catch many defects, some misuses of language are easy for humans to miss but straightforward for a static...
Coding Style Guidelines and MISRA C
Critical embedded software should follow a well-defined set of coding guidelines, enforced with comprehensive static checking tools, with essentially no deviations. MISRA C is an example of an accepted set of such coding...
