Re: [boost] Fw: [atomic] review results

Subject: Re: [boost] Fw: [atomic] review results
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2011-11-08 07:20:38

Helge Bahmann wrote:
> Tim Blechmann wrote:
>
> > > this could be avoided by using
> > > boost::interprocess::atomic<>, which will associate a
> > > spinlock with each instance ... or by using std::atomic on
> > > c++11 compilers.
>
> While this problem is definitely an argument in favour of
> embedding the spinlock into each atomic, I am still concerned
> as this introduces incompatibility with std::atomic
> implementations which may eventually bite someone hard (data
> structure size, expectations -- changing boost to "using
> std::atomic" might have grave consequences, and it's a
> transition path I would like to keep open)

You could just conditionally compile two choices when a platform's support is insufficient: a potentially incompatible implementation or nothing.  If a user selects the latter, they may choose to use boost::interprocess::atomic instead.  You might also provide the incompatible implementation via a distinct name in the latter case so the user could choose that instead.

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