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.6 required=5.0 tests=BAYES_00,FROM_WORDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,af986aa93b89733e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-09 18:26:04 PST Path: supernews.google.com!sn-xit-03!supernews.com!nntp.cs.ubc.ca!newsfeed.stanford.edu!paloalto-snf1.gtei.net!news.gtei.net!enews.sgi.com!newscon06.news.prodigy.com!prodigy.com!newsmst01!postmaster.news.prodigy.com!newssvr10-int.news.prodigy.com.POSTED!not-for-mail From: "Ken Garlington" Newsgroups: comp.lang.ada References: <1Q_z6.474$VI4.153258056@newssvr10-int.news.prodigy.com> Subject: Re: V-22 Osprey and exception handling Organization: ex-FlashNet, now Prodigy X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <3htA6.809$j53.240510015@newssvr10-int.news.prodigy.com> NNTP-Posting-Host: 65.65.208.71 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr10-int.news.prodigy.com 986865855 6207069 65.65.208.71 (Mon, 09 Apr 2001 21:24:15 EDT) NNTP-Posting-Date: Mon, 09 Apr 2001 21:24:15 EDT Date: Tue, 10 Apr 2001 01:24:15 GMT Xref: supernews.google.com comp.lang.ada:6682 Date: 2001-04-10T01:24:15+00:00 List-Id: Ted Dennison" wrote in message news:knjA6.787$FY5.40878@www.newsranger.com... : In article <1Q_z6.474$VI4.153258056@newssvr10-int.news.prodigy.com>, Ken : Garlington says... : > : > wrote in message : >news:djPz6.9$kb.47845@news1.i1.net... : >: 3. In most systems, the occurrence of such failures is accommodated by the : >: FCS design and does not constitute what I would consider to the : >appropriate : >: use of Ada's exception handling mechanism. (In the design of a typical : .. : >: I use exception handling for conditions that should "never" happen like : >: maybe a floating point overflow. In an FCS, the accommodation of a : >: hydraulic failure does not fall into that category. : > : >I think my point was more along the lines that this is another case where a : >function that was part of the failure handling requirements, actually : >contributed to an accident instead. : : There really isn't enough information in the report to even go that far. For all : we know, it could have been caused by code that was *not* handling possible : failures when it should have been. Until the other report that is to go into the : aircraft itself comes out... Which report is this? : its just too premature to say (for all we know, that : report might go completely against this one, and blame "pilot error"). It : certainly *way* premature to be talking about specific language features. I think you've missed the point. I'm not suggesting that a particular language feature caused the V-22 crash. Please re-read the original post. : --- : T.E.D. homepage - http://www.telepath.com/dennison/Ted/TED.html : home email - mailto:dennison@telepath.com