IIRC the old persistance library defined facilities for input and output
using the RFC-1014 XDR: External Data Representation Standard. The new
serialization library doesn't seem to include such archive classes and
leaves it up to the user to write these.
Now I don't mean to dispute the decision, but I'd just like to know what
the rationale for it was.
Secondly, I have a nit about the documentation. In the reference section
about the 'Definition of New Archive Formats' it is said that:
'The archive format is specified by implementing the virtual functions
of the base class.'
I think it would be clearer if the documentation also stated all those
virtual functions that one should implement, so that the user wouldn't
have to read archive.hpp. Perhaps a simple example should be provided.
Say, a rot13 text stream or something.
Regards,
Dirk Gerrits
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
- [boost] Serialization Submission version 6 Robert Ramey
- Re: [boost] Serialization Submission version 6 Vladimir Prus
- [boost] help with porting new container algorith... Thorsten Ottosen
- RE: [boost] Serialization Submission version 6 Dirk Gerrits
- RE: [boost] Serialization Submission version 6 Robert Ramey
- Re: [boost] Serialization Submission version 6 Vladimir Prus
- Re: [boost] Serialization Submission version 6 Robert Ramey
- Re: [boost] Serialization Submission version 6 Vladimir Prus
- Re: [boost] Serialization Submission version 6 Robert Ramey
- Re: [boost] Serialization Submission version 6 Vladimir Prus
- [boost] Re: Serialization Submission version... Alberto Barbati
- Re: [boost] Serialization Submission version 6 Robert Ramey
- Re: [boost] Serialization Submission version 6 Vladimir Prus
- [boost] Re: Serialization Submission version 6 Alberto Barbati