Re: V-22 Osprey and exception handling

["Ken Garlington" <Ken.Garlington@computer.org>]

Ted Dennison" <dennison@telepath.com> 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...
: >
: ><pab49162@hotmail.com> 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