Re: NASA/JPL Rules for writing Critical Software

2015-01-09 Thread Robert burner Schadek via Digitalmars-d
On Thursday, 8 January 2015 at 23:37:38 UTC, Walter Bright wrote: http://pixelscommander.com/wp-content/uploads/2014/12/P10.pdf from the document (Rule 5): A typical use of an assertion would be as follows: if (!c_assert(p >= 0) == true) { return ERROR; } that is just bad code. IMO I'm

Re: NASA/JPL Rules for writing Critical Software

2015-01-09 Thread 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" wrote in message news:m8n4c2$2ovq$1...@digitalmars.com... The interesting part of those rules is that in the end, C + rules + static analyzer ends up b

Re: NASA/JPL Rules for writing Critical Software

2015-01-09 Thread Paulo Pinto via Digitalmars-d
On Friday, 9 January 2015 at 10:37:43 UTC, Mike James wrote: "Walter Bright" wrote in message news:m8n4c2$2ovq$1...@digitalmars.com... http://pixelscommander.com/wp-content/uploads/2014/12/P10.pdf Misra is also a good set of guidelines to follow... http://www.misra.org.uk/ -=mike=- The in

Re: NASA/JPL Rules for writing Critical Software

2015-01-09 Thread Mike James via Digitalmars-d
"Walter Bright" wrote in message news:m8n4c2$2ovq$1...@digitalmars.com... http://pixelscommander.com/wp-content/uploads/2014/12/P10.pdf Misra is also a good set of guidelines to follow... http://www.misra.org.uk/ -=mike=-

NASA/JPL Rules for writing Critical Software

2015-01-08 Thread Walter Bright via Digitalmars-d
http://pixelscommander.com/wp-content/uploads/2014/12/P10.pdf