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: 103376,af986aa93b89733e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-09 07:10:05 PST Path: supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!newsfeed.stanford.edu!feed.textport.net!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Ted Dennison Sender: usenet@www.newsranger.com References: <1Q_z6.474$VI4.153258056@newssvr10-int.news.prodigy.com> Subject: Re: V-22 Osprey and exception handling Message-ID: Date: Mon, 09 Apr 2001 14:08:16 GMT NNTP-Posting-Host: 209.208.22.130 X-Complaints-To: abuse@newsranger.com X-Trace: www.newsranger.com 986825296 209.208.22.130 (Mon, 09 Apr 2001 10:08:16 EDT) NNTP-Posting-Date: Mon, 09 Apr 2001 10:08:16 EDT Organization: http://www.newsranger.com Xref: supernews.google.com comp.lang.ada:6656 Date: 2001-04-09T14:08:16+00:00 List-Id: 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, 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. --- T.E.D. homepage - http://www.telepath.com/dennison/Ted/TED.html home email - mailto:dennison@telepath.com