Re: Structured exception information

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Tue, 16 Jan 2007 17:50:46 GMT, Jeffrey Carter wrote:

> Dmitry A. Kazakov wrote:
>> 
>>    procedure Foo raises Foo_Error; -- Compile error!
> 
> Generally, subprograms should raise exceptions because of precondition 
> violations. If the preconditions are met, the subprogram should not 
> raise an exception (barring things that are beyond the developer's 
> control, such as running out of memory). So it would be better to 
> associate a subprogram with a list of preconditions with the exception 
> raised if each is violated:
> 
> function Arccoth (Coth : Real) return Real
> when abs Coth < 1.0 raise Invalid_Coth;
> 
> procedure Time_Limited (X : in Integer)
> when X = 0 raise Zero_X and
> when Ada.Calendar.Clock >=
>       Ada.Calendar.Time_Of (Year    => 2010,
>                             Month   => 1,
>                             Day     => 1,
>                             Seconds => 0.0)
> raise Too_Late;

Totally disagree.

A precondition violation is not an exceptional state, it is a bug. Bugs
fundamentally cannot be handled within the same program. This "exception"
should propagate in the visual debugger and further into the head of the
code maintainer, If you want.

The difference becomes obvious if you consider that there might well be
valid program states corresponding to the end of a file. But there cannot
be any valid and consistent state in which there would exist x such that
cosh(x)<1.

Therefore their handling strategies are quite different as well. Bugs
propagating exceptions is the worst debugging nightmare. A precondition
violation shall stop immediately to prevent further harm and to make a
inspection possible. Exceptions are just a method of flow control.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de