on Tue Aug 07 2007, "Peter Dimov" <pdimov-AT-pdimov.com> wrote:
"Note that the requirements for being release-ready are transitive; if a library has dependent libraries, it isn't considered release-ready if it breaks any of those dependent libraries."
This is sensible but it can prevent progress if these failures are caused by the dependencies rather than the core library. Two arbitrary shared_ptr examples: (1) the serialization library in 1.32 relying on implementation details, (2) Spirit using the long deprecated make_shared spelling of weak_ptr::lock.
That's a real problem. We need a way to override the normal process when things like this happen. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com