From: Hughes, James (jhughes_at_[hidden])
Date: 2007-05-09 11:38:26
Hi Robert,
I have an inkling that I may understand what the feature/bug is, and
this seems to coincide with what you say here.
I'm wondering whether I can use non-intrusive serialisation for the out
of library classes in the main library, and remove the intrusive code
from the sub-library to get round the problem. I'll give it a go
tomorrow - just had the yearly round of pay rises, so need to go and
drown my sorrows.
James
> -----Original Message-----
> From: boost-users-bounces_at_[hidden]
> [mailto:boost-users-bounces_at_[hidden]] On Behalf Of Robert Ramey
> Sent: 09 May 2007 02:57
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] Serialisation across libraries.
>
> I strongly suspect that this is a manifestation of a subtle
> bug/feature of serialization 133 and maybe 1.34.
>
> Its hard to explain in a short email. But the short version
> is that serialization for the same type is included more than
> one place - a shared library as well as mainline or another
> shared library.
>
> So you can consider how your code is distributed among the
> libraries with the idea that serialization for the same type
> is not spread accross various shared libraries.
>
> Robert Ramey
>
> Hughes, James wrote:
> > Hi Robert,
> >
>
Snipped a load...
This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law. If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system. If you
have any questions about this e-mail please notify the sender
immediately.