From: vicente.botet (vicente.botet_at_[hidden])
Date: 2008-08-30 22:21:33
----- Original Message -----
From: "Emil Dotchevski" <emil_at_[hidden]>
Sent: Saturday, August 30, 2008 7:33 PM
Subject: Re: [boost] [exception][policy]
> On Sat, Aug 30, 2008 at 5:29 AM, vicente.botet <vicente.botet_at_[hidden]>
>> BTW, if current_exception works for any exception, we don't need anymore
>> that boost::throw_exception use boost::enable_current_exception, isn't
> More accurately, on platforms where current_exception can work for any
> exception without support from enable_current_exception,
> enable_current_exception can be noop.
More accurately, on platforms where current_exception can work for any
exception, the file containing boost::throw_exception MUST not depend on the
file containing enable_current_exception.
>> I'm not questioning the usefulness of boost::exception_ptr. I'm only
>> that in the current release, current_exception do not works for any
>> exception (do not transfer every exception between threads) as required
>> 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
>> the one of the current release. What objections do you have to my
> What use case do you have in mind?
Sorry, but I dont understand your question. What use case do I have in mind
for what? Maybe you can question is related to:"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."