Re: [boost] Serialization and dynamic "fallback" to base classes

From: Robert Ramey (ramey_at_[hidden])
Date: 2007-12-07 19:47:03

In this context this is not so easy.

a new archive contains data for a new class.  The old program has
never seen this new class, so it doesn't know how much information
to skip.

Of course this could be addressed if you really wanted to.

But, as you've mentioned, no one has asked for this.  Maybe
there is a good reason for that.

BTW, the next version has addressed issues with DLLS so
that you could ship a new archive along with a shared library
which contains the code to de-serialize it. The old program
can use the new shared library - as long as the base class
itself hasn't changed

Robert Ramey

Edgars Irmejs wrote:
> I've always liked to maintain as much as possible old versions of
> software for users who don't want to upgrade. That includes not
> destroying their existing functionality (receiving "bus" class
> objects). Maybe it's just plain wrong...
>
> Thanks anyway!