|FROM ||Ruben Safir
|SUBJECT ||Subject: [NYLXS - HANGOUT] [firstname.lastname@example.org: Re: [accu-general] Who uses C?]
----- Forwarded message from Balog Pal -----
Date: Wed, 6 Apr 2011 21:39:39 +0200
From: Balog Pal
Subject: Re: [accu-general] Who uses C?
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
----- Original Message ----- From: "Bj?rn Fahller"
>> Let me google it for you
>> Why do you think it is false? I mean, what C++ compiler would you use to
>> write high-reliability systems?
> Define high-reliability.
Indeed. I seriously doubt the risk in this field would come from the
quality of the compiler (especially if not evaluated alone but in a
Also IIRC Cameau has good reputation and if someone considers C good
for the purpose compiler-wise, they can create the mix.
As I visualise the risks, the code generator/optimizer seem to be the
tricky part -- things messed up at the C++ level would either make the
code not compile, or to obvious errors (or rather theoretical ones).
While the code generator is likely shared.
And if you use a "runtime env" like for java, that in itself is more
risk than anything, isn't it?
accu-general mailing list
----- End forwarded message -----