Re: [boost] Merging to release

Subject: Re: [boost] Merging to release
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2012-07-16 07:41:49

Tim Blechmann wrote:
>
> >> * some compilers (at least gcc-4.3) implement rvalue
> >> references, but stl containers do not provide emplace
> >> semantics. so one does not have precise control via
> >> BOOST_NO_RVALUE_REFERENCES.
> >
> > I don't think BOOST_NO_RVALUE_REFERENCES (now
> > BOOST_NO_CXX11_RVALUE_REFERENCES) should be used as any
> > indication of presence/absence of emplace member functions.
> > That would be another macro entirely.
>
> true, especially as it is a compiler vs stdlib thing.

Perhaps it would be useful to have a manifest constant that indicates a lack of complete support for a particular header -- a conforming implementation would not define that constant, then -- plus constants for each specific feature, but only as the need arises.  Thus, in one conditional, a library could determine full conformance and otherwise can test for the various pieces wanted.

> but then the `correct' way is to have one preprocessor symbol
> for each container ...

New feature manifest constants should be added as the need arises, not preemptively, to avoid unnecessary preprocessing bloat.

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