Emil Dotchevski wrote:
it a good idea for the shared_ptr serialization to be implemented in terms of the T * object contained in a boost::shared_ptr<T>?
The whole serialization library is built on that concept. It's the best idea I could come up with.
I mean, for example std::string isn't serialized in terms of the char * object it contains, right?
whether std::string contains a char * is an internal implemention detail. Serialization of std::string does use (If I remember correctly) the function which returns a char * - but maybe not. std::string is not a good example though as it is a special case for a couple of reasons.
Perhaps more to the point, what plans do we have for serializing std::shared_ptr using boost::serialization?
The current implementation of serialization of boost::shared_ptr depends only upon the published public interface of boost::shared_ptr. (personally I have some complaints about that public interface though). Assuming that std::shared_ptr has the same published interface as boost::shared_ptr - I would expect the serialization implemenation would be the same. Robert Ramey
Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode