Re: [Boost-bugs] [Boost C++ Libraries] #5341: Patch to improve shared library behavior with serialization

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #5341: Patch to improve shared library behavior with serialization
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-04-04 07:05:08

#5341: Patch to improve shared library behavior with serialization
----------------------------------------------+-----------------------------
  Reporter:  Aaron Barany <akb825@…>          |       Owner:  ramey                              
      Type:  Patches                          |      Status:  new                                
 Milestone:  To Be Determined                 |   Component:  serialization                      
   Version:  Boost 1.46.0                     |    Severity:  Problem                            
Resolution:                                   |    Keywords:  serialization shared_libraries dlls
----------------------------------------------+-----------------------------

Comment (by Aaron Barany <akb825@…>):

 To answer your questions:\\
 a) I haven't re-run them yet, but when I get a chance I will look into it
 and reply with the results.\\
 b) If there's anything in particular that you aren't sure about, I'll try
 my best to clarify.\\
 c) The problem with the previous usage of BOOST_ARCHIVE_OR_WARCHIVE_DECL()
 was that it required all template instantiations of the map to be
 imported/export in exactly the same way. By using the method described by
 Microsoft, it allows you to specify different import/export settings per
 template instantiation. This is a requirement if you want to create an
 archive compiled outside of the boost_serialization dll.

 I can certainly understand your skepticism. I've had to deal with a lot of
 subtle issues with serialization in the codebase I'm working in, which is
 very large and complex, and spread out across many DLLs. (it was so much
 simpler before we started using DLLs... but not using them had its own set
 of problems) After going through how the registration system works, and
 performing a lot of both thought and real world experiments, I'm pretty
 sure it won't cause any backwards compatibility issues. However, I know
 that despite my best efforts I still could have missed something, so this
 will certainly take a lot of testing in other use cases to verify.

 I'm curious, do any of the tests in library_test use files saved from
 earlier versions of boost serialization? If so, then that can help put
 some fears to rest, though we can't be completely sure until it's used in
 more real world situations.

 Aaron

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