| 
|
Quote: coding rules for safety-critical applications in C; e.g., simple control flow, short functions, assertions, check args, avoid pointers, no warnings
Topic:
programming style
Topic:
safety critical systems
Group:
repetitive control
Topic:
heap memory management
Quotation Skeleton
For fairly pragmatic reasons, … the following 10 [coding] rules primarily target C … [safety-]critical applications written in C. … Restrict all code to very simple control flow … [p. 96] Give all loops a fixed upper bound. … Do not use dynamic memory allocation after initialization. … no more than about 60 lines of code … The code's assertion density should average to minimally … Declare all data objects at the smallest possible … Each calling function must check the return value … the caller. … [p. 97] the preprocessor must be limited to the … The use of pointers must be restricted. … All code must compile without warnings. … Developers are currently using this rule set experimentally … [Jet Propulsion Lab] to write mission-critical software, with encouraging results Google-1 Google-2
Copyright clearance needed for quotation.
Additional Titles
Quote: all loops should have a fixed upper bound Quote: for safety-critical code, do not use dynamic memory allocation after initialization
Topic: programming style (47 items)
Topic: safety critical systems (32 items)
Group: repetitive control (7 topics, 117 quotes)
Topic: heap memory management (33 items)