Ron Hashimshony wrote:
> Hi all boost users,
> We have been using boost.serialization for years. We want to move
> from 1.33 to 1.47 and encountered a problem.
> Many of our classes are abstract, and the derived are defined with
> BOOST_CLASS_EXPORT_GUID.
> At one point in time, a new class (B) was added that derives from a
> class that was defined with the BOOST_CLASS_EXPORT_GUID macro (A).
> It all worked well in 1.33. In 1.47, when we get to de-serialize
> class A, we get an exception of unregistered class.
> We traced it down, and found out that if we remove the derived class
> (B), it
> works fine, but this is not an option, and then the derived class (B)
> cannot be de-serialized from the file...
> If there any way to bypass this problem? was there a change made that
> broke this
> functionality?
> Many Thanks!
> Ron
>

I believe this is a problem introduced in version 140 which is under
investigation. Which type of archive are you using?

Robert Ramey

Hi Robert,
We are using XML archives only at the moment. we want to use the portable binaries as well.
Any idea when this problem will be solved?
Thanks.