From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Jeffrey Carter <spam.jrcarter.not@spam.not.acm.org>
Newsgroups: comp.lang.ada
Subject: Re: F-22 ADA Programming
Date: Tue, 28 Oct 2014 16:59:28 -0700
Organization: Also freenews.netfront.net; news.tornevall.net;
 news.eternal-september.org
Message-ID: <m2pakq$99g$1@dont-email.me>
References: <a510f410-56ea-46a6-9f3c-021a2389b936@googlegroups.com>
 <f4e05c1d-e52e-44f1-84e1-3814e526c469@googlegroups.com>
 <m2jvqm$qpc$2@dont-email.me>
 <dfa977d6-1458-4d8a-b226-15a759e321d6@googlegroups.com>
 <220f97ab-9aa2-4961-b140-2b271c3ab99a@googlegroups.com>
 <slrnm4ulto.nrc.lithiumcat@nat.rebma.instinctive.eu>
 <m2on9t$tv6$1@dont-email.me>
 <99759c3f-a35f-4745-a8fd-2fb6ab6fb1aa@googlegroups.com>
 <m2p0g5$4d0$1@dont-email.me>
 <48dc1630-8e7d-4e29-8bdd-53d74932d9d0@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 28 Oct 2014 23:59:24 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="206f88a41f45fc94d25d07d064d738e2";
	logging-data="9520"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+KArvC5NRZvX3h0ERu6MgXErvdAocuVQY="
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
In-Reply-To: <48dc1630-8e7d-4e29-8bdd-53d74932d9d0@googlegroups.com>
Cancel-Lock: sha1:a1JRAU1oIzRpDZFhHJYk3Uhvlxc=
Xref: news.eternal-september.org comp.lang.ada:22883
Date: 2014-10-28T16:59:28-07:00
List-Id: <comp.lang.ada>

On 10/28/2014 02:37 PM, Adam Beneschan wrote:
> 
> (2) Accept the position, and plan to use the skills you possess in writing 
> safe, secure code, to influence the rest of the team to adopt coding (and 
> testing) practices that result in code that's as reliable as anything
> written in Ada would be.
> 
> (And if anyone believes #2 is impossible, because the C++ language somehow 
> emits  unsafeness waves that travel through the air and into your monitor and
> turn all your carefully-written safe code into unsafe code ... OK, I'm being
> silly, but that just isn't correct.  That's one of the reasons I reacted so
> strongly to Jeff's earlier post, because it seemed to equate using an unsafe
> language to writing unsafe code, which of course is wrong.  You can write
> safe code in any language.  It may take a little more work in some languages;
> but if you're aware of the need to write safe code, and are disciplined, it
> can be done.  And if you're not, Ada isn't going to help.)

I don't think #2 is impossible, just unlikely, given the kind of people who like
C++.  You're more likely to be ostracized by your fellow coders for writing
"inefficient code", labeled "not a team player" by manglement, and fired.

I'm not sure about the "any language", either. We have decades of experience
that show that humans cannot write critical networking S/W safely in C. I would
say that some people can write safe code in (almost) any language, and most
people will write unsafe code in any language.

-- 
Jeff Carter
"My mind is a raging torrent, flooded with rivulets of
thought, cascading into a waterfall of creative alternatives."
Blazing Saddles
89