[boost] [lockfree] freelist_stack::allocate and freelist_stack::deallocate should not be private

Subject: [boost] [lockfree] freelist_stack::allocate and freelist_stack::deallocate should not be private
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2012-09-01 16:06:19

Hey all,

Currently, the allocate/deallocate functions et.al. in
lockfree::detail::freelist_stack are private. This inhibits reusing this
class for implementing other lock-free datastructures as it's not possible
to allocate anything which has not a constructor taking 0, 1, or 2 arguments
(those are supported explicitly by exposing overloads for
freelist_stack::construct).

Would it be possible to make the mentioned functions 'protected' instead?

Regards Hartmut
---------------
http://boost-spirit.com
http://stellar.cct.lsu.edu