on Wed Nov 12 2008, joaquin-AT-tid.es wrote:
David Abrahams escribió:
Not that I really need this feature, but what is going to prevent the library from doing the usual thing it does when deserializing T here?
The call to reset_object_address than ensues: as every different object of non_tracking<T> gets reassigned to a unique element in the helper table, it's impossible that Boost.Serialization tracking capabilities mistakenly take one object t1 as the same as a previous t2 just because their (stack-based) addresses coincide. This is not supressing tracking, but effectively implies that it'll never impact the serialized stuff.
It impacts the *size* of the serialized stuff, which is my only motivation for turning off tracking. -- Dave Abrahams BoostPro Computing http://www.boostpro.com