Re: [Boost-users] [serialization] DLL woes

If you mean place everything related to serialization in one DLL, then yes, that will obviously work. But in practice that's hardly a useful solution, since then any library that depends on X now depends on all other libraries that depend on X. I've looked at the register_type function (I assume it is related to this), but I'm not too familiar with the inner workings of the serialization lib. What is it exactly that is registered for each type and why is it an error if this occurs twice?

Place code to implement X in its own DLL.

Robert Ramey