Everyone who writes safety critical software should read this
bearophile
bearophileHUGS at lycos.com
Fri Nov 1 08:03:46 PDT 2013
Walter Bright:
> ...
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.
Bye,
bearophile
More information about the Digitalmars-d
mailing list