|
Boost : |
From: Eric Woodruff (Eric.Woodruff_at_[hidden])
Date: 2002-11-14 10:14:31
type_info is not portable in the slightest.
"Vahan Margaryan" <vahan_at_[hidden]> wrote in message
news:003401c28bee$7fbc4f40$4f09a8c0_at_lan.mosaic.am...
----- 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 class
name.
> (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 for
template classes. type_info does this for you.
Regards,
-Vahan
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk