Re: [boost] Boost and exceptions

Subject: Re: [boost] Boost and exceptions
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2012-06-25 12:43:32

Mathias Gaunard wrote:
> On 06/22/2012 02:23 PM, Stewart, Robert wrote:
>
> > In hindsight, I agree with Robert's assertion that there
> > should have been a replacement function,
> > boost::exception::throw_exception() or similar, to introduce
> > the new functionality.  Whether the existing function needed
> > to be deprecated is a separate issue.  The result is that
> > libraries could knowingly choose the new version, and a
> > dependency on Boost.Exception, or, if warranted, stick with
> > the old.
>
> That would be a terrible idea.
>
> The whole point of the system is that there is a single place
> where you enable Boost.Exception support for all libraries.

The original point of boost::throw_exception() was to provide a fallback when exception support is not available.  That it now enables Boost.Exception support is the problem for some.

> If some libraries were allowed to stick to non-
> Boost.Exception-enabled boost::throw_exception, then you
> couldn't transfer those exceptions between threads.

You could in C++11, but that's another matter.

There is no Boost policy that requires Boost.Exception support.  If you think there should be, then lobby for it.  Until then, library authors and maintainers can choose to not support Boost.Exception, yet their libraries should be supported when exceptions are not.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer                     using std::disclaimer;
Dev Tools & Components
Susquehanna International Group, LLP  http://www.sig.com

________________________________

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.