Re: [boost] [serialization] Support for multiple class name strings

From: Janek Kozicki (janek_listy_at_[hidden])
Date: 2007-03-16 11:04:55

Zach Laine said:     (by the date of Fri, 16 Mar 2007 09:02:04 -0500)

> > IMHO this is the best example demonstrating that sometimes using a
> > class name as a GUID is not the best idea. If Zach from the very
> > beginning used a custom string (different that the class name) as a
> > GUID, this thing would have never happened. Am I right?
> 
> This was my thought as well.  In fact, I'm going to switch all our
> BOOST_CLASS_EXPORT(T) macros to BOOST_CLASS_EXPORT_GUID(T, "[T's
> canonical name]") macros, and leave a giant note for others to do the
> same ("Here there be dragons", etc.).  In light of this problem, I
> would say that while use of BOOST_CLASS_EXPORT() is convenient, it is
> ultimately a maintenance burden.

Robert, can you please put this example in the documentation? It
would demonstrate clearly to new users why they should use
BOOST_CLASS_EXPORT_GUID instead.

Anyway, IMHO adding a support for multiple GUIDs is the best route to
better support archives compatibility.

-- 
Janek Kozicki                                                         |