Re: [boost] [serialization] export.hpp changes from 1.37 to 1.38

Subject: Re: [boost] [serialization] export.hpp changes from 1.37 to 1.38
From: Robert Ramey (ramey_at_[hidden])
Date: 2009-02-14 18:58:34

Chard wrote:
> This is pretty much what we had originally, but, like I said, we
> could not compile it because of the number of symbols generated. This 
> probably highlights limits with MSVC7.1 because I believe the
> COFF limit has been increased in later versions, but (for the moment)
> it does mean we only have one choice: register_type<>.
>
> The file-splitting workaround, which was okay with 1.37:
>
> File1.cpp
> #include <boost/archive/text_oarchive.hpp>
> #include <boost/archive/text_iarchive.hpp>
> #include "t.hpp"
> #include <boost/serialization/export.hpp>
> BOOST_CLASS_EXPORT(T)
>
> File2.cpp
> #include <boost/archive/binary_oarchive.hpp>
> #include <boost/archive/binary_iarchive.hpp>
> #include "t.hpp"
> #include <boost/serialization/export.hpp>
> BOOST_CLASS_EXPORT(T)
>
> is no good for 1.38.

That is a surprise to me. it would seem that we're trying
to address two issues at the same time.  One creating
of an extended type info record and the other instantiating
per archive code. We'look into it.

Robert Ramey