Hi Reece,
The boost sandbox is a CVS repository used by Boost developers to hold
works-in-progress so they are available to other Boost developers.
Thank you for your indications. I' ve from long time put eternity on
sourceforge at the address:
http://sourceforge.net/projects/eternity-it
It co
Robert Ramey wrote:
>>> iv) requirement to have separt save/load code for serialization
>>> functions
>
>>I though about it just recently, and stubmled upon the issue of
>>const-correctness. Probably, separate save/load is OK, since I don't know
>>any good alternative solution.
>
> I was always
Hi Nicola,
Nicola Santi wrote:
> As I wrote in previous posts I do not write in english very well, so I
> could have made some misunderstandings. I try to clarify:
>
> > I'm afraid I don't like this approach. You have 3 ways to serialize an
> > object:
> > 1. Call operator <<
> > 2. Call put_
Robert Ramey <[EMAIL PROTECTED]> writes:
> It turns out that ALL the issues raised in the review, including
> those that I dismissed, are being addressed. I didn't really intend
> to do this I had resolved to improve the quality of the implementation
> and leave most of the feature decisions un
Vladimir Prus wrote:
>> iii) requirement to pre-register classes to be saved as pointers
>> through a base class
>Was it ever considered a problem. You surely have to register a class in
>order to deserialize it (Java can create a class given its name, but we're
>in C++).
I refering to the issue
Vladimir Prus wrote:
b) versioning at the class level
I implemented a binary serialisation library at my previous work place
that was very similar to what has been described here.
As for versioning, we left it up to the class. But implemented it in
all classes. All classes stored a version n
Hi Robert,
Robert Ramey wrote:
> Nicola, Vladimir et.al
>
> I submitted a serialization library for review last november.
>
> It was rejected for inclusion in boost for a number of reasons which
> I will attempt to summarize as follows:
[...]
> b) Certain usage features
> ii) inconvenient type
Hi Nicola,
Nicola Santi wrote:
> >4. I don't understand how serialization of base classes should be done.
>
> In derive class serialization method remember to call the serialization
> method of base class.
>
> void Derived::serialize( bin_archive &stream) {
> // first base class serialization
