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-22 18:25:51
#5341: Patch to improve shared library behavior with serialization
----------------------------------------------+-----------------------------
Reporter: Aaron Barany <akb825@â¦> | Owner: ramey
Type: Patches | Status: closed
Milestone: To Be Determined | Component: serialization
Version: Boost 1.46.0 | Severity: Problem
Resolution: wontfix | Keywords: serialization shared_libraries dlls
----------------------------------------------+-----------------------------
Changes (by ramey):
* status: new => closed
* resolution: => wontfix
Comment:
"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 looked at this again and I can't see how this differs from using the
BOOST_ARCHIVE macros above. It could be that the BOOST_ARCHIVE macros are
not implemented correctly ... but the idea and method is identical as far
as I can tell. In addition to the properly declaring export and import,
they support the boost autolib fuctionality. If you want to investigate
the implementation of these macros, feel free, but there is no way I'm
going to do this in a different way than all the other boost libraries do.
Robert Ramey
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/5341#comment:4> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:06 UTC