Everyone who writes safety critical software should read this
Walter Bright
newshound2 at digitalmars.com
Fri Nov 1 21:03:47 PDT 2013
On 11/1/2013 8:03 AM, bearophile wrote:
> Everyone who writes safety critical software should really avoid languages
> unable to detect integral overflows (at compile-time or run-time) in all normal
> numerical operations, and languages that have undefined operations in their
> basic semantics.
>
> So Ada language is OK, C and D are not OK for safety critical software.
I think you're missing the point. Improving the quality of the software is not
the answer to making fail safe systems.
More information about the Digitalmars-d
mailing list