5 Jan
2007
5 Jan
'07
6:41 p.m.
"Emil Dotchevski" <emildotchevski@hotmail.com> writes:
Compare this to the example I provided a few levels up: foo.h does not include any header files and yet defines how objects of class foo are to be serialized. Correct me if I'm wrong but I think that that example is essentially compatible with boost serialization; it is the intended use of BOOST_CLASS_EXPORT in header files that introduces the physical coupling I'm complaining about.
Is there something wrong with defining your classes in foo.hpp and exporting them in a foo_serialization.hpp that isn't included by foo.hpp? -- Dave Abrahams Boost Consulting www.boost-consulting.com