How do the folks at JPL write the code that will land a 2000-pound robot on Mars without a single glitch? Much of their success is no doubt due to their talent and dedication, but it doesn’t hurt that they have very strict coding standards (PDF). Among the requirements for C-language code at JPL:
- Compile with all warnings enabled; use static source code analyzers.
- Do not use direct or indirect recursion.
- Do not use dynamic memory allocation after task initialization.
- Declare data objects at smallest possible level of scope.
- Check the validity of values passed to functions.
- Make the order of evaluation in compound expressions explicit.
- Do not use expressions with side effects.
- Make only very limited use of the C pre-processor.
- Use short functions with a limited number of parameters.
- Do not cast function pointers into other types.
The JPL code standards are based on the 2004 MISRA-C coding standard. MISRA was originally designed for automotive applications, but was later adapted to other safety-critical systems where computer glitches can have dire consequences, like remote control locomotives. Some of the requirements parallel specifications of the language ADA, which was originally designed for safety-critical applications like missile guidance systems.
The 2009 version of the standard is available as a PDF from jpl.nasa.gov.
Have an amazing project to share? Join the SHOW-AND-TELL every Wednesday night at 7:30pm ET on Google+ Hangouts.
Join us every Wednesday night at 8pm ET for Ask an Engineer!
Learn resistor values with Mho’s Resistance or get the best electronics calculator for engineers “Circuit Playground” – Adafruit’s Apps!
Maker Business — “Finally — some data on whether crowdfunding is a good investment or not”
Wearables — Sample code is your new best friend
Electronics — Meaningful gains
Sorry, the comment form is closed at this time.