From: Greg Colvin (gregory.colvin_at_[hidden])
Date: 2003-03-21 10:48:35
std::exception used to have a why() member that returned the list of
exceptions leading to the one caught. Is that part of what you want?
On Friday, Mar 21, 2003, at 03:58 America/Denver, Alisdair Meredith
> Darren Cook wrote:
>> I wanted something like the call stack that shows in python or java
>> when an
>> uncaught exception occurs; if you're also suggesting a snapshot of
>> vars/parameters then I'll be in heaven and may never need to fire up a
>> debugger again :-).
> This is exactly NOT what I am interested in though!! For me this is a
> function of debugger/tools. I specifically want to build up context
> a human-readable message to explain why some process failed to the user
> of the software.
> The difference is error-handling as opposed to bug-tracking, and it
> could be there are two libraries (maybe relying on a common subset of
> behaviour) lurking here. I'm not sure which of these two problems
> Trevor was proposing to address, but think it is important such a
> distinction is made early.
> Team Thai Kingdom
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk