|
Boost : |
From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-11-13 11:40:09
----- Original Message -----
From: "Kevin S. Van Horn" <kevin.vanhorn_at_[hidden]>
> > > In addition, I would suggest that even when you do throw an exception,
the
> > > exception object should include the file and line number. (See
discussion
> > > below for overview.html.)
> >
> > I don't think I agree about that, except when exceptions are thrown as
part
> > of the undefined behavior resulting from a failed precondition. Even
then,
> > as code becomes increasingly encapsulated, the originating file and line
> > become increasingly useless.
>
> However it's done, I think you need to provide sufficiently detailed
> information to identify the library call that went wrong and the precise
> nature of the error.
Then you need to find a way to produce a complete core dump. You never know
what might have gone wrong (the underlying cause) by the time you detect a
precondition violation.
-Dave
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk