Earlier quoted context omitted.
Most high-reliability software is still written in C or other languages in the algol family. For the highest level of assurances, often the binary code must be mapped back to the source code (to reduce the chances of a compiler bug introducing errors), and doing so in languages that are higher-level than C becomes problematic. If someone were to formally verify the correctness of a particular higher-level language im…
NASA did use Lisp in the past.
NASA C Style Guide [pdf]
31–33 of 33 posts
Re: NASA C Style Guide [pdf]
#32Earlier quoted context omitted.
> Style is concerned with the appearance of the code, and is largely subjective. Many languages, like Common Lisp and Java, have got this nailed: the same style is used everywhere. In the C world, there are endless arguments about levels of indentation, the position of braces, etc. I'm struggling with where to first disagree with this. Some style guides deal only with code appearance, but they can also include things…
We're disagreeing about the meanings of style vs. standards here. I'm using style in the commonly accepted sense, e.g. "hair stylist", "stylish", "all style and no substance." Maximum function lengths and cyclomatic complexity are important but I'd put those under standards. Lisp gives you a lot of flexibility regarding how you do things, but once you choose a way, that constrains how your code should be laid out, i.…
Indeed we are. I'm considering "style guide" as a noun phrase to include many things that you would call standards, and comes from the definition of style "a manner of doing something."
Re: NASA C Style Guide [pdf]
#33I see the brace goes on the next line, as it should: if(condition) { expression... } instead of the obfuscated form: if(condition) { expression... }