"JOAQUIN LOPEZ MU?Z" wrote:
So, I think providing archive types specialized for serializing specific types basically breaks down the architectural design of B.S, which is based on the separation of type-agnostic archives and archive-agnostic serialization code: this is too good to depart from.
I totally understand and am in total agreement. I made an exception to this general rule for shared_ptr which I felt I had to do at the time. But I think you missed the main point of my last message. The 1.33 system has an api for attaching helpers to to an archive class. This was only used (as far as I knew) and only needed to address the special problems associated with the serialization of shared_ptr. This introduced code into the library for handling one special case - which we both agree is a bad idea. Now you're telling me that you need it for other types - well that was news to me. So I'm thinking that a better solution might be to create a class "helper manager" which contains the functionality of the 1.33 and mixing in THIS class at the bottom of the hierarchy. So things would give you back the functionality of 1.33 while still removing inappropriate API decoration of the base classes. Robert Ramey
Joaquín M López Muñoz Telefónica, Investigación y Desarrollo _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost