Re: [Boost-bugs] [Boost C++ Libraries] #3658: Remove dependency on static initialization/destruction order

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3658: Remove dependency on static initialization/destruction order
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-01-13 08:02:52

#3658: Remove dependency on static initialization/destruction order
-------------------------------+--------------------------------------------
  Reporter:  andysem           |       Owner:  joaquin  
      Type:  Feature Requests  |      Status:  closed   
 Milestone:  Boost 1.42.0      |   Component:  flyweight
   Version:  Boost 1.41.0      |    Severity:  Problem  
Resolution:  invalid           |    Keywords:           
-------------------------------+--------------------------------------------
Changes (by joaquin):

  * status:  reopened => closed
  * resolution:  => invalid

Comment:

 I'm re-closing this old one, as the suggestions on the mailing list
 discussion seem to me too cumbersome to implement, and basically break the
 orthogonality of the different concepts (factory, holder, values.) As
 suggested there, you can define your own holder that basically does not
 delete the factory, at the cost of a memory leak (if it can be called a
 leak, as this is not your normal leak where memory usage increases over
 time, which is the problematic case.)

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