Re: [Boost-users] [Serialize] Conflict between Serialize and PIMPL?

I think we're talking about serializing through a pointer to an abstract base class. Boost serialization supports - through the "register type" and/or "export" functionality. You'll have to look at the documentation. when serialization is restoring objects through the abstract pointer, /it/ thinks it is responsible for instantiating all classes, including the derived classes. do end up with /two/ instances of the private implementation class, one of which is just hanging in mid-air? Not if you do it as described in the documantion and tests. -- View this message in context: http://boost.2283326.n4.nabble.com/Serialize-Conflict-between-Serialize-and-... Sent from the Boost - Users mailing list archive at Nabble.com.