On Tue, Jun 3, 2014 at 4:04 PM, Beman Dawes <bdawes@acm.org> wrote:
A FAQ might be helpful. Likely questions:
Q. Are there breaking changes for Boost libraries?
Q. Are there recommended (although not breaking) changes for Boost libraries?
Q. Are there breaking changes for user code?
Q. Are there recommended (although not breaking) changes for user code?
Not denying the FAQ usefulness, I can answer these questions. No breaking changes have been made, all the code that previously compiled should keep compiling. boost/utility/empty_deleter.hpp has been deprecated in favor of boost/core/null_deleter.hpp. Including the deprecated header will display warnings pointing to the new header. Eventually (not in 1.56 for sure) empty_deleter.hpp will be deleted. Implementation from all headers that were moved to Boost.Core is now in boost/core. The old headers now simply forward to the new ones (without warnings). It is recommended to include the new headers directly, although the changes are not necessary. I'm not sure if we're going to deprecate the old headers, but if we will, I'd say we should add warnings first to start the deprecation period.