From: Beman Dawes (bdawes_at_[hidden])
Date: 2002-11-04 12:10:30
At 07:58 PM 11/3/2002, David Abrahams wrote:
>Beman Dawes <bdawes_at_[hidden]> writes:
>> At 12:48 AM 11/3/2002, Kevin S. Van Horn wrote:
>> >Throwing an exception, on the other hand, causes the stack to be
>> unwound, >thus throwing away all of that information. When debugging,
>> throwing an
>> >exception on a logical (programmer) error is the last thing in the
>> world I
>> >want to happen.
>> Surely your debugger allows you to trap the exception at the point it
>> is thrown,
>If you're lucky enough to be running under the debugger, and to have
>that breakpoint set, when the problem is detected, then you're home
>free. That's a big IF.
The context Kevin gave was "When debugging", which I assumed meant running
under the debugger. I also tend to keep most exception traps on when
debugging, and that helps too.
But don't get me wrong, being able to replace the behavior might be a nice
feature, if carefully thought out.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk