From: <wemagor@sym1.cca|rockwell.nospam (Wayne Magor)
Subject: Re: Improving Ada Exceptions
Date: 1997/11/08
Date: 1997-11-08T00:00:00+00:00 [thread overview]
Message-ID: <640d4n$l431@castor.cca.rockwell.com> (raw)
In-Reply-To: 63ll1g$7f8$2@trumpet.uni-mannheim.de
My biggest gripe with Ada exceptions is that there is no indication in the
spec as to what exceptions a subprogram can raise (or propagate).
You cannot know for sure that *your* code is correct until you examine the
bodies of all the subprograms you call for "raise" statements. You then
must examine all the subprograms that they call, and so forth.
Perhaps a tool is needed that does this type of analysis. Then, at least
comments can be added to every subprogram spec indicating what exceptions
it could raise. Knowing this, you should be able to create a tool that
tells you if any of your code is propagating exceptions that you didn't
expect to be propagating. Then, if you don't want it to be propagated
you can handle it in your subprogram.
Recovering from unexpected exceptions is important in critical applications,
but it's difficult to achieve.
next prev parent reply other threads:[~1997-11-08 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-03 0:00 Improving Ada Exceptions Marc Wachowitz
1997-11-08 0:00 ` Wayne Magor [this message]
1997-11-10 0:00 ` Samuel T. Harris
-- strict thread matches above, loose matches on Subject: below --
1997-10-26 0:00 Ray Blaak
1997-10-27 0:00 ` Chris Morgan
1997-10-27 0:00 ` Alan E & Carmel J Brain
1997-10-27 0:00 ` Larry Kilgallen
1997-10-27 0:00 ` Tucker Taft
1997-10-27 0:00 ` Stephen Leake
1997-10-27 0:00 ` Tom Moran
1997-10-27 0:00 ` James S. Rogers
1997-10-30 0:00 ` Balmacara9
1997-11-03 0:00 ` Richard A. O'Keefe
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox