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=-0.9 required=5.0 tests=BAYES_00,CTE_8BIT_MISMATCH
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: 103376,e6a2e4a4c0d7d8a6
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-21 00:22:45 PST
Path: 
 archiver1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.vmunix.org!feed.news.nacamar.de!bnewspeer01.bru.ops.eu.uu.net!emea.uu.net!news2.vol.cz!not-for-mail
From: =?iso-8859-2?B?T25k+GVqIFR16G79?= <tucny@flexlanguage.com>
Newsgroups: comp.lang.ada
Subject: Re: status of PL/I as a viable language
Date: Fri, 21 Feb 2003 09:14:01 +0100
Organization: A && L soft, s.r.o.
Message-ID: <oprkxqhntnmzo9uz@news.vol.cz>
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>
 <1045769690.126389@master.nyc.kbcfp.com> <2lb33b.7d6.ln@jellix.jlfencey.com>
 <1045772065.590669@master.nyc.kbcfp.com>
NNTP-Posting-Host: mail.alsoft.cz
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2; format=flowed
X-Trace: news.vol.cz 1045814936 81153 195.250.140.18 (21 Feb 2003 08:08:56
 GMT)
X-Complaints-To: abuse@vol.cz
NNTP-Posting-Date: Fri, 21 Feb 2003 08:08:56 +0000 (UTC)
In-Reply-To: <1045772065.590669@master.nyc.kbcfp.com>
User-Agent: Opera7.0/Win32 M2 build 2637
Xref: archiver1.google.com comp.lang.ada:34331
Date: 2003-02-21T09:14:01+01:00
List-Id: <comp.lang.ada>

> And the people who used the Patriot battery for too long (again, assuming
> this incident is true) caused the failure, not the software.
>
> Which is to say, complex systems can have complex failure modes,
> and the fact that some programming languages will catch simple
> errors isn't going to help at all with the complex ones.

Not in all cases. Here a complex failure (failure of a Patriot battery) was 
originally caused by a simple overflow error. And as someone already 
pointed
out, the complex failure would have never happened if the originating 
simple error was detected and handled properly.

So there is a class of complex failures that are caused by simple errors, 
and
so these complex failures can be eliminated by eliminating (detecting & 
handling)
simple errors.

-- 
Ond�ej Tu�n�