|
Boost Users : |
From: Robert Ramey (ramey_at_[hidden])
Date: 2006-02-09 10:17:02
I've included that facility and a test which demonstrates it.
test_no_rtti demonstrates how it can be used with a
type_info facility which uses the string associated with the
type via BOOST_CLASS_EXPORT.
Other than that it hasn't been really tested/explored extensively.
After doing all this, it occurred to me that it RTTI would still
be required to serialize the std::vector etc. This could be
worked around by some combination of the above
a) implemented BOOST_CLASS_EXPORT for those
serializations in the library
b) making a custom extended_type_info class which uses some
other yet to be determined method.
c) avoiding serialization of types not exported via pointers. That
is, only types serialized via pointers required RTTI. (at least
that's the intention - better test this!!)
Robert Ramey
Alexandre Gacon wrote:
> Hi,
>
> I would like to use the serialization library inside one of my
> project which do not use the RTTI. I produce a first version using
> boost::serialization::extended_type_info to produce the key
> associated to the class.
>
> Is it possible to use my own keys instead of the extended_type_info
> class to serialize my classes ?
>
> Thank you,
>
> Alexandre Gacon
> Project Manager
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net