From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2005-02-03 12:47:13
> The problem is that a red square due to this change (that could have
> been avoided if you had given us warning) will mask other problems, so
> it slows development. For instance, John put in some type_traits
> changes that inevitably broke something, somewhere, but for him to find
> his errors in the sea of red will not be easy.
Ok we both made changes that inevitably broke something. Why don't you look
on this other way around?
> > Anyway 3 years should've been
> > enough to get rid of tools that were announced deprecated.
> Sure. The problem is that the Test lib is one of those core libraries,
> like type_traits, where changes ripple through and can cause a lot of
That's why I am have very limitted amount of time when I could make changes
and do not want to wait for weeks after announcement making sure everybody
had time/ heard about it.
> We just need to know when deprecated bits are being removed,
> because it's very likely that some of us didn't even know they were
> deprecated until they were gone.
Ok. I am ready to make this a policy: One week notice for removed depricated
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk