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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e6a2e4a4c0d7d8a6 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-02-20 12:14:27 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!nntp.abs.net!uunet!dca.uu.net!ash.uu.net!spool0900.news.uu.net!reader0901.news.uu.net!not-for-mail Date: Thu, 20 Feb 2003 15:14:25 -0500 From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030130 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: status of PL/I as a viable language References: <3E51908E.9CCA3412@adaworks.com> <8Gh4a.7455$_c6.743959@newsread2.prod.itd.earthlink.net> <3E51ABCE.5491B9A2@adaworks.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> In-Reply-To: <2lb33b.7d6.ln@jellix.jlfencey.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Organization: KBC Financial Products Message-ID: <1045772065.590669@master.nyc.kbcfp.com> Cache-Post-Path: master.nyc.kbcfp.com!unknown@nightcrawler.nyc.kbcfp.com X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) NNTP-Posting-Host: 204.253.250.10 X-Trace: 1045772067 reader1.ash.ops.us.uu.net 12567 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:34300 Date: 2003-02-20T15:14:25-05:00 List-Id: Vinzent Hoefler wrote: > In that particular case I'd assume, yes. Some kind of reboot/restart > would have helped. Which actually sounds just like what's happening in the F-22 case, doesn't it? Things run for a few hours, then have to be rebooted. That's not exactly a hallmark of a reliable system. > It was proven that this exception could never occur in normal operation Sounds pretty much the same to me - a design assumption is violated, and the programming language error handlers start doing stuff that is completely inappropriate to the situation out in the world. > Using the same code in Ariane 5 with the same assumptions as were valid > for Ariane 4 was the failure, not the code itself. 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.