|
Boost : |
From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2007-09-30 22:36:23
On 9/30/07, Emil Dotchevski <emil_at_[hidden]> wrote:
> > > <snip>
[snip]
> > My biggest concern is bad_alloc being thrown and the exception being
> > replaced. It might not be as bad for most cases, but may be critical
> > in others.
>
> Suppose we catch a bad_alloc, then (for reasons that are hard for me
> to imagine) we throw something_else, which derives from
> boost::exception, and we attempt to stuff it with all kinds of info.
> The two possible outcomes are, it either works fine, or we get another
> bad_alloc instead of something_else.
>
> I don't see how this could cause any problems (any more than the
> original bad_alloc would).
I'm actually trying to avoid the possibility of bad_alloc being throw
by not allocating anything.
>
> Emil Dotchevski
-- Felipe Magno de Almeida
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk