From: Vahan Margaryan (vahan_at_[hidden])
Date: 2002-11-14 11:15:41
----- Original Message -----
Eric Woodruff wrote:
> type_info is not portable in the slightest.
I realize that. I just pointed out that it's not so convenient to have
user-supplied string ids because of the template classes.
> "Vahan Margaryan" <vahan_at_[hidden]> wrote in message
> ----- Original Message -----
> From: "Robert Ramey" <ramey_at_[hidden]>
> Sent: Thursday, November 14, 2002 5:45 PM
> Subject: Re: [boost] Serialization Submission version 6
> > register_cross_program_class_identifier<class T>(const char *id="T")
> > This would be invoked for each class declaration. Now we have
> > a portable id associated with each class - exactly what we need.
> > Polymorphic pointers would archive this tag and use it
> > to determine the proper class to construct on loading.
> > The default class identifier would be the text representation of the
> > (note: in general not necessarily the same as type_info.name() )
> > which is going to be sufficent for almost all cases.
> The problem that usually arises from this is having to make up class ids
> template classes. type_info does this for you.
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk