Boost logo

Boost Users :

From: Henrik Jacobsson (henrik.jacobsson_at_[hidden])
Date: 2005-05-13 02:31:51

> cyclic objects can't be serialized. cyclic object pointers can be
> serialized with no special effort.

A simple, and probably naive, idea... Since pointers mean no problems and
objects do, would it not be possible to have an option
"serialize_object_as_pointer" and for containers "serialize_members_as_pointers"
in the library, as a means to circumvent this? That way one would not have to
change the implementation of all containers of cyclic objects into containers of

Alternatively, or additionally, within the cyclic object themselves, it would be
nice if it was possible to serialize the pointer without serializing its
contents, i.e. creating only an index in the archive, making it up to the user
to make sure that the object is later serialized with that index to adress it.
The order of serialized contents will then be in the order of preference of the
user. Deserialization may become a nightmare then, I suppose... But still, it
would be nice with that kind of control over the order of serialization...

// Henrik Jacobsson

> Robert Ramey
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]

Boost-users list run by williamkempf at, kalb at, bjorn.karlsson at, gregod at, wekempf at