On 13 Aug 2012, at 19:51, Greg Ercolano wrote: > JPL's C language coding standards: > > http://lars-lab.jpl.nasa.gov/JPL_Coding_Standard_C.pdf > > Many items some will find obvious, and some are specific to embedded > hardware and real time hardware control. Still, and interesting read. > 31 rules in approx. 18 pages.
Though that is only because the printed section elides all the MISRA stuff which they call up, but can not print as they do not own the copyright to it... So, not really 31 rules, more like many thousands of picky, nit-picking, b*&^%cks that make it hard to do anything actually useful. As you can possibly guess, I am frequently called upon to code within the confines of some arbitrary interpretation of the MISRA guidelines, and I seldom find them helpful... Really, I had a block of code (maybe 20 K sloc) that threw nearly 6K warnings when fed through our MISRA checker. I spent the time to fix them (the customer required it) even though I knew they were spurious, and at the end we had found exactly zero actual bugs, and produced an embedded binary blob that was bit-for-bit identical to my original. So that was worth doing, then. True. Story. Good static analysis tools though, that really is time well spent. But most of the MISRA rules are Not Helpful. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
