RE: [boost] casts, exceptions, and asserts

From: Fernando Cacciola (fcacciola_at_[hidden])
Date: 2001-10-26 18:12:24

----- Original Message -----
From: Kevin S. Van Horn <kevin.vanhorn_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Friday, October 26, 2001 7:50 PM
Subject: RE: [boost] casts, exceptions, and asserts

> My preference for logical errors (ones that the programmer could
> reasonably have avoided) is usually for the program to abort and dump
> core.  This allows me to go in with a debugger and see what the state of
> the program was when the error occurred.  If you throw an exception the
> stack unwinds, and you lose lots of important debug information.  I
> realize that the abort behavior is unacceptable for some industrial
> environments, so let me suggest that there be a preprocessor symbol one
> can set to choose whether violated preconditions (that the implementor
> chooses to check) cause an exception or just abort and dump core.
>
Yes, there is no doubt that these are the two usually required behaviours,
and the choice is application specific.
The framework must be somehow configurable, at least, up to the choice of
one of this two behaviours.

Fernando Cacciola
Sierra s.r.l.
fcacciola_at_[hidden]
www.gosierra.com