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=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 101deb,3488d9e5d292649f
X-Google-Attributes: gid101deb,public
X-Google-Thread: 103376,e6a2e4a4c0d7d8a6
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-20 11:09:53 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!chcgil2-snh1.gtei.net!chcgil2-snf1.gtei.net!news.gtei.net!news.binc.net!kilgallen
From: Kilgallen@SpamCop.net (Larry Kilgallen)
Newsgroups: comp.lang.pl1,comp.lang.ada
Subject: Re: status of PL/I as a viable language
Date: 20 Feb 2003 13:09:46 -0600
Organization: LJK Software
Message-ID: <HVDh3osH+3al@eisner.encompasserve.org>
References: <mHZ0a.42983$jM5.108891@newsfeeds.bigpond.com>
 <nRg1a.190899$HG.32437469@news4.srv.hcvlny.cv.net>
 <3E51908E.9CCA3412@adaworks.com>
 <8Gh4a.7455$_c6.743959@newsread2.prod.itd.earthlink.net>
 <3E51ABCE.5491B9A2@adaworks.com> <b2spe6$p23$1@helle.btinternet.com>
 <3E5273DE.2050206@cox.net> <3E531E6F.BDFB2599@adaworks.com>
 <3E546C45.4010406@cox.net> <3E54F926.441D5BB5@adaworks.com>
 <1045763933.848350@master.nyc.kbcfp.com>
 <42EA55F4BE83950E.F1DA277C2FDC157B.C804C1C52FE95D65@lp.airnews.net>
NNTP-Posting-Host: eisner.encompasserve.org
X-Trace: grandcanyon.binc.net 1045768119 23393 192.135.80.34 (20 Feb 2003
 19:08:39 GMT)
X-Complaints-To: abuse@binc.net
NNTP-Posting-Date: Thu, 20 Feb 2003 19:08:39 +0000 (UTC)
Xref: archiver1.google.com comp.lang.pl1:4366 comp.lang.ada:34292
Date: 2003-02-20T13:09:46-06:00
List-Id: <comp.lang.ada>

In article <42EA55F4BE83950E.F1DA277C2FDC157B.C804C1C52FE95D65@lp.airnews.net>, "John R. Strohm" <strohm@airmail.net> writes:

> Are you trying to say you DON'T want to catch those "gross errors of
> coding - buffer overruns, null pointer accesses, arithmetic overflow, etc."?
> 
> Any one of those "gross errors of coding" can and will crash an embedded
> system, or, worse, cause it to fail in a bad way.  It was an overflowed
> counter that caused a Patriot battery not to engage an incoming Scud,
> resulting in the deaths of several U.S. servicemen.

Can you provide a citation for that incident ?