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

Subject: Re: [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-03 10:11:08

#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     
Resolution:                    |    Keywords:              
-------------------------------+--------------------------------------------

Comment (by timblechmann):

 making allocate protected. deallocate should not be required, as one can
 still use the destruct method.

 however in general it would be cleaner to use an api like this:
 {{{
 template <class... Args>
 T * construct(Args&&... args)
 }}}

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