F-35 Joint Strike Fighter Coding Standard Documentation

OH: "Any sufficiently complex DoD coding standard is indistinguishable from Ada"

This made me laugh:<p>AV Rule 6 Each deviation from a “shall” rule shall be documented in the file that contains the deviation. Deviations from this rule shall not be allowed, AV Rule 5 [specifying the process to deviate from a "shall" rule] notwithstanding.

AV Rule 25 (MISRA Rule 127) The time handling functions of library &#60;time.h&#62; shall not be used.<p>Yes everyone reinventing their own broken flat tire date routines is the way go. If they used the same silly rule on the F22 that explains <a href="http://blog.utest.com/international-date-line-bug-caused-fighter-aircraft-systems-crash/2010/02/" rel="nofollow">http://blog.utest.com/international-date-line-bug-caused-fig...</a><p>Time related code is really hard to write.

The rules seem quite reasonable and less strict than what I had expected. The libraries section mentions "Only DO-178B Level A certifiable" libraries. Are any common open source libraries among those and is there a list available somewhere? Another HN thread mentioned that there are certified C++ standard libraries but I couldn't find any vendor of such.

The buses used on aircraft are interesting. ARINC 429 is used for commercial aircraft. MIL-STD-1553 is used for military aircraft. STANAG3838 is the EU equivalent.<p>(<a href="http://en.wikipedia.org/wiki/ARINC_429" rel="nofollow">http://en.wikipedia.org/wiki/ARINC_429</a>)<p>(<a href="http://en.wikipedia.org/wiki/MIL-STD-1553" rel="nofollow">http://en.wikipedia.org/wiki/MIL-STD-1553</a>)<p>Wikipedia suggests a logic analyser for development. That's handy, but you'd be best starting with good continuity buzzing; I've seen some of the cables being made and it's a bit of a bodge.

Interesting that this document is stored on Bjarne Stroustrup's (creator of C++) web site at AT&#38;T Labs. I wonder whether he had any part in writing it?

I remember reading this some years ago (unless this is a new version)<p>Dear C++ programmers: follow this! (with exceptions accordingly)

My brother works for Lockheed writing technical manuals. He is the guy who writes those things. I mean, I can't even read them without runing away screaming.<p>He studied IT, but never got a job in it. I keep bugging him to get a job coding, but he thinks he can't.<p>Anyone got a job coding for someone who writes those amazingly complex manuals?

There's an error in Rule 52. They specifically say variables shouldnt have any capital letters but their example does.

if(enemy=true) FireWeapons(); // (sic)

With rules like that, this plane is going to be vapourware for a long time!