Re: [Boost-users] [serialization] 1.35 problemwith explicitinstantiation

From: Robert Ramey (ramey_at_[hidden])
Date: 2008-04-13 19:39:04

Dan Thill wrote:

I'm certainly sympathetic.

But I fee that now we've resolved several big problems which
were really annoying.

a) The library should now be thread-safe - without any locking !
b) The situation of having serialization code in DLLS - and possibly
more than one was never considered when the library was made.
I believe this has now been addressed.
c) Export was always confusing.  Hopefully now it is less so.  Also
in using the old advice, code was instantiated whether it was used or not.

So, I AM sympathic as the annoys the hell out of me when it happens to me.

You could make a separt little module which you would compile into
your main which would include all the BOOST_CLASS_EXPORT
macros for your types.  Then the linker would get the code from
your static library.

Robert Ramey

> I'm sorry if I sound irate.  I'm just extremely frustrated.  I went
> through all the effort to put the 1.34.1 serialization into its own
> library in order to fix compilation time problems in our product.  And
> then, a few days later, 1.35 is released, breaking everything.  (and
> for various platform issues, we need to move to 1.35).
>
> -Dan