Re: [boost] [lockfree] tagged_ptr as a separate library

Subject: Re: [boost] [lockfree] tagged_ptr as a separate library
From: Philipp Moeller (philipp.moeller_at_[hidden])
Date: 2012-03-30 07:56:01

Tim Blechmann <tim_at_[hidden]> writes:

>> In the review of lockfree it has been suggested that tagged_ptr should
>> make it into the public API of lockfree.
>> 
>> Wouldn't it make sense to move it into a separate library entirely? It
>> would possibly get more exposure and cross-platform ports. The technique
>> itself also requires some extra documentation. And it might find it's
>> way into a release earlier than lock-free itself.
>
> for now i prefer to keep it an implementation detail. but maybe it can be 
> exposed to the public API in future. how now i'd like to wait until there are 
> some std::atomic implementation which can actually compile the tagged_ptr. i 
> hope boost.lockfree will be in 1.50, still waiting for boost.atomic, though 

Isn't tagged_ptr also useful even when it is not used atomically?

Sorry, for the mix-up of the delays. I was under the (wrong) impression
that boost.atomic is waiting for boost.lockfree.

>
> cheers, tim
>