News for hackers. Stuff that matters.
Re:NASA C Style Guide [pdf] by pmiller2 on Saturday November 19, 2016 @07:00PM (#12996442)
I'm a little disturbed that this doesn't make any mention of when C is even appropriate. I know if I were an astronaut, I'd be concerned about the code running on the vehicle I was on.
Re:NASA C Style Guide [pdf] by aidenn0 on Saturday November 19, 2016 @07:19PM (#12996511)
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 implementation, then it would start to become usable. Most GCed languages are out though due to the fact that hard-realtime GC algorithms require an excess of CPU and RAM to run correctly, and vehicles going into space are often several generations of hardware behind, as new radiation-hardened CPUs come out only rarely.

Re:NASA C Style Guide [pdf] by pjmlp on Sunday November 20, 2016 @03:49AM (#12997953)
NASA did use Lisp in the past.
Re:NASA C Style Guide [pdf] by aidenn0 on Sunday November 20, 2016 @05:16PM (#13001612)
Super nit-pick but if you are talking about the DS1, I believe it was JPL under contract for NASA.