-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Pavlo Korzhyk Sent: 03 May 2007 22:25 To: boost-users@lists.boost.org Subject: Re: [Boost-users] [Serialisation] One last GUID question - I hope.
"The macro BOOST_CLASS_EXPORT_GUID associates a string
class. In the above example we've used a string rendering of the class name. If a object of such an "exported" class is serialized
pointer and is otherwise unregistered, the "export" string is included in the archive. When the archive is later read, the string
used to find the class which should be created by the serialization library. ****This permits each class to be in a separate
.... literal with a through a literal is header file
along with its string identifier****. There is no need to maintain a .... Is the document misleading here, or have I missed something??
It says that the class declaration may be placed in a separate header, but that doesn't mean BOOST_CLASS_EXPORT_GUID must be placed to that header too :) When you create a separate header for the class, usually you also create a separate .cpp for it. Place BOOST_CLASS_EXPORT there and everything will work fine.
WBR, Pavlo Korzhyk ICQ#155870780
Thanks Pavlo, that's what I have done. Bit of a pain when you have a header only class though... James
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.