4 Aug
2009
4 Aug
'09
12:38 a.m.
On 3 Aug 2009, at 15:34, Roland Kaminski wrote:
The code is full of such "dangerous" optimizations but most of them can be somehow handled. It is optimized to be as cache-friendly as possible that is why I would like to not remove this one. A hook during deserialization would be exactly what I need. I could also imagine other worarounds but all of them are very ugly.
Look at this part of the documentation: http://www.boost.org/doc/libs/1_39_0/libs/serialization/doc/serialization.ht... and overload load_construct_data and save_construct_data for your type Matthias