Re: [Boost-bugs] [Boost C++ Libraries] #5876: Serialization - tracking of non-versioned classes

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #5876: Serialization - tracking of non-versioned classes
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-07-15 20:44:02

#5876: Serialization - tracking of non-versioned classes
-------------------------------------+--------------------------------------
  Reporter:  ybungalobill@…          |       Owner:  ramey        
      Type:  Bugs                    |      Status:  assigned     
 Milestone:  To Be Determined        |   Component:  serialization
   Version:  Boost 1.47.0            |    Severity:  Showstopper  
Resolution:                          |    Keywords:               
-------------------------------------+--------------------------------------
Changes (by ramey):

  * status:  new => assigned

Comment:

 "I find it counter-intuitive. I expect objects serialized as objects to
 mean 'by value' and not be tracked, while objects serialized by pointer to
 mean 'by reference' and be tracked. Anyway it's your choice and I won't
 criticize it."

 This was a design decision made at the very beginning as an optimization.
 Basically the idea was that there was no need to include the pointer
 deserialization code unless the the item was serialized explicitly via a
 pointer.  In retrospect, this turns out to be questionable.  It's possible
 for the same object to be serialized multiple times even though it's never
 through a pointer. Actually, this needs to be re-thought in detail - which
 I'm not likely to do any time soon.

 One thing you might consider is explicitly setting the implementation
 level to include tracking so that items get tracked regardless of how they
 are used.

 Robert Ramey

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