NASA/JPL Rules for writing Critical Software

[eles via Digitalmars-d]

On Friday, 9 January 2015 at 11:50:04 UTC, Paulo  Pinto wrote:
> On Friday, 9 January 2015 at 10:37:43 UTC, Mike James wrote:
>> "Walter Bright" <newshound2 at digitalmars.com> wrote in message 
>> news:m8n4c2$2ovq$1 at digitalmars.com...

> The interesting part of those rules is that in the end, C + 
> rules
> + static analyzer ends up being the type of language that the C
> designers decided to ignore.

In their defense, not really. The line they usually use is that 
"C provides freedom". One cannot deny that C provides the freedom 
to be bent according to the MISRA and JPL standards.

Yes, it is not sane by default. But it gives one the freedom to 
be sane or to be mad...