Re: [boost] [exception][policy]

From: Emil Dotchevski (emil_at_[hidden])
Date: 2008-08-30 13:33:18

On Sat, Aug 30, 2008 at 5:29 AM, vicente.botet <vicente.botet_at_[hidden]> wrote:
> BTW, if current_exception works for any exception, we don't need anymore
> that boost::throw_exception use boost::enable_current_exception, isn't it?

More accurately, on platforms where current_exception can work for any
exception without support from enable_current_exception,
enable_current_exception can be noop.

> I'm not questioning the usefulness of boost::exception_ptr. I'm only stating
> that in the current release, current_exception do not works for any
> exception (do not transfer every exception between threads) as required by
> n2179. What is worst is that the final user can not do anything for the
> exceptions thrown by 3pp libraries that do not use
> boost::enable_current_exception or boost::throw_exception.
>
> My proposal allows the final user to complete *intrusively* the list of
> exceptions for which current_exception will work, having as default behavior
> the one of the current release. What objections do you have to my proposal?

What use case do you have in mind?

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode