From: David Abrahams (dave_at_[hidden])
Date: 2003-10-01 09:56:17
Samuel Krempp <krempp_at_[hidden]> writes:
> If I got it right, Robert is reluctant to have deserialization require
> default-constructability, even private
I certainly agree that it's a nasty constraint. I think I can see
only one way to achieve non-intrusive deserialization in portable C++:
the deserialization function gets an address into which the object
will be constructed with placement new. The main downside of this
approach is that it becomes difficult to deserialize subobjects.
-- Dave Abrahams Boost Consulting www.boost-consulting.com