Re: [boost] [config] Proposed BOOST_NOEXCEPT_NOTHROW macro

Subject: Re: [boost] [config] Proposed BOOST_NOEXCEPT_NOTHROW macro
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2012-08-29 07:48:29

Beman Dawes wrote:
> On Tue, Aug 28, 2012 at 6:27 PM, Vicente J. Botet Escriba
> <vicente.botet_at_[hidden]> wrote:
> > Le 28/08/12 23:22, Beman Dawes a écrit :
> >
> >> The three current BOOST_NOEXCEPT* macro variants miss the
> >> case where C++03 code has a "throw()" throw-specifier.
> >> Classes that derive from standard library exceptions need
> >> this to avoid breaking code on C++03 compilers.

I think I suggested the need for that in the beginning.  It is an important case as you've found.

> >> I'm not enamored with the BOOST_NOEXCEPT_NOTHROW name, so
> >> feel free to offer suggestions for alternate names.
> >
> > I will cal it BOOST_NOEXCEPT_OR_NOTHROW.
>
> I considered that, but was put off by its length.
> BOOST_NOEXCEPT_OR_NOTHROW is clearer and the transition from
> throw() to noexcept is confusing, so let's got with
> BOOST_NOEXCEPT_OR_NOTHROW

I agree that the name is long, but it is clear.

What about BOOST_NOTHROW?  It doesn't transition well to an all-C++11 world (only noexcept), but both throw() and noexcept mean the function emits (or should emit) no exceptions, so the name conveys the right idea.  Maybe BOOST_THROWS_NOTHING to avoid the old connotation of "NOTHROW"?

_____
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.