Re: [boost] [serialization]Boost.Serialization1.33.0BreaksSerializationCodeinDLLs

From: martin.ecker_at_[hidden]
Date: 2005-09-06 01:27:41

Hello,

Robert Ramey wrote:
> What I'm worried about are the virtual function calls routed through the 

> base class vtable. 

Can you direct me to where in the Boost.Serialization code this is 
happening? I'd like to have a look at this. What base class are you 
referring to?

> Its not clear to me that its an unavoidable problem.  Just including the 

> header for a serializable type won't trigger inclusion of the indicated 
> static variables.  One has to include archive code and instantiate it 
for 
> the specific serializable type by invoking and << or >> operator on it. 
I 
> don't believe the problem would ever arise if archve headers were 
included 
> in only one DLL.

Of course you're right. Simply including the headers doesn't trigger 
anything, but for example using BOOST_CLASS_EXPORT in a DLL and then 
using archives from the main application should trigger the problem 
for type info objects, if I'm not mistaken. Also using archives from 
multiple DLLs, which is not an uncommen scenario for us, will trigger 
multiple instances of static members in header files.

Best Regards,
Martin

TAB Austria
Haiderstraße 40
4052 Ansfelden
Austria
Phone: [phone]
Fax: [phone]
E-mail: martin.ecker_at_[hidden]
http://www.tab.at