[Boost-bugs] [Boost C++ Libraries] #7321: freelist_stack::allocate and freelist_stack::deallocate should not be private

Subject: [Boost-bugs] [Boost C++ Libraries] #7321: freelist_stack::allocate and freelist_stack::deallocate should not be private
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-09-02 22:22:16

#7321: freelist_stack::allocate and freelist_stack::deallocate should not be
private
------------------------------+---------------------------------------------
 Reporter:  hkaiser           |       Owner:  timblechmann
     Type:  Bugs              |      Status:  new         
Milestone:  To Be Determined  |   Component:  lockfree    
  Version:  Boost 1.52.0      |    Severity:  Problem     
 Keywords:                    |  
------------------------------+---------------------------------------------
 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?

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/7321>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.