Boost logo

Boost :

From: Martin Slater (mslater_at_[hidden])
Date: 2005-08-24 05:13:28

> library contains code to serialize "shared_ptr" types. Should the
> Serialization library contain similar code for every potential Boost type,
> so should each type include the code?
> If the latter is the answer, then does:
> class my_type {
> friend class ::boost::serialization::access;
> //...
> };

I just ran into this again when I needed to serialize a
boost::dynamic_bitset and with porting our codebase over to use 1.33
bringing across the modification I made to boost::filesystem::path for
serialization. If there is a chance that these will get incorporated
into cvs I will go to the effort of writing and configuring test cases
for them and submit them (I did submit sode and tests a long time ago
for filesystem::path but unfortuantly they never made it in so I'm
reluctant to do more unless there is willing by the library authors to
have them). It seems there should be a concerted effort to get all of
boost being able to serialise out of the box as it leaves the library as
a whole feeling somewhat disjointed. I may have some free time in the
near future so I could be persuaded to go through implementing /
incorpating existing patches for serialisation for other boost libraries.



No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.15/80 - Release Date: 23/08/2005

Boost list run by bdawes at, gregod at, cpdaniel at, john at