"Robert Ramey" <ramey@rrsd.com> writes:
David Abrahams wrote:
"Robert Ramey" <ramey@rrsd.com> writes:
However, since I happen to be intimately familiar with what's required here, I'm willing to work up a complete patch for you if you'll tell me I won't be wasting my time. It would give me the chance to the "instantiate arbitrary code from a class template body" abstraction into a separate sub-library.
That would be ideal from my point of view - please feel free to check it in.
Great! I ask only that you update the documentation, to note that archive authors should invoke BOOST_SERIALIZATION_DECLARE_ARCHIVE to make their archives availabe to this mechanism, and to remove the warning about header ordering. You have two choices about how I'll handle backward compatibility: 1. Require that all user-written archive headers be updated with the next release of this library 2. Leave enough of the old mechanism in place so that existing code will still work as long as it follows the header ordering rule with respect to export.hpp okay, maybe three choices: 3. Tell me that archive authors outside the library *already* have to invoke some macro that I don't know about, and I can add the effect of BOOST_SERIALIZATION_DECLARE_ARCHIVE to that macro's implementation. Please let me know which of those angles I should pursue. -- Dave Abrahams Boost Consulting www.boost-consulting.com