on Sun Nov 09 2008, "Robert Ramey" <ramey-AT-rrsd.com> wrote:
LOL - well for you maybe.
Note one thing. Its not so much the code change, its all the other stuff that this generates:
a) code change =>
b) documentation change/ehancement. This takes some effort to explain why serialzation is trapped or not trapped as a "side effect" of setting the tracking attribute.
c) user support - Even if one takes the requisite effort to explain it, one will have to continually re-explain it as users have what they consider surprising behavior
c) new tests - not a huge deal but still a minor pain - UNLESS something doesn't work with this or that obscure compiler.
I'll consider it in more detail when I have the time.
Yeah, I'm familiar with that response. I've given it many times myself ;-)
Robert Ramey
P.S. I quick peek at the code below make me think that the line (serialization::tracking_level<T>::value == track_never), might better be replaced with: (serialization::tracking_level<T>::value <= track_never),
Easier for me, you say? I never would have gotten that. -- Dave Abrahams BoostPro Computing http://www.boostpro.com