Subject: Re: [boost] Release managers: Boost.Thread breaking changes in 1.53
From: Lars Viklund (zao_at_[hidden])
Date: 2012-12-31 11:59:57
On Mon, Dec 31, 2012 at 07:38:55AM -0800, Marshall Clow wrote:
> On Dec 31, 2012, at 6:17 AM, Lars Viklund <zao_at_[hidden]> wrote:
> > This list thread (heh) is pretty much the _first_ I ever hear about this
> > debacle. None of the "it's deprecated releases ago" have I ever seen,
> > and I, unlike most people, read the lists and (used to) hang in #boost.
> > What chance does your average packager or developer have to notice this?
> It was in the release notes:
> â¢ Deprecated Features: Deprecated features since boost 1.50 available only until boost 1.55. These deprecated features will be provided by default up to boost 1.52. If you don't want to include the deprecated features you could define BOOST_THREAD_DONT_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0. Since 1.53 these features will not be included any more by default. Since this version, if you want to include the deprecated features yet you could define BOOST_THREAD_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0. These deprecated features will be only available until boost 1.55, that is you have yet 1 year to move to the new features.
> â¢ Time related functions don't using the Boost.Chrono library, use the chrono overloads instead.
> â¢ Breaking changes when BOOST_THREAD_VERSION==3 (Default value since Boost 1.53): There are some new features which share the same interface but with different behavior. These breaking features are provided by default when BOOST_THREAD_VERSION is 3, but the user can however choose the version 2 behavior by defining the corresponding macro. As for the deprecated features, these broken features will be only available until boost 1.55.
> â¢ #6229 C++11 compliance & Breaking change: Rename the unique_future to future following the c++11.
> â¢ #6266 C++11 compliance & Breaking change: thread destructor should call terminate if joinable.
> â¢ #6269 C++11 compliance & Breaking change: thread move assignment should call terminate if joinable.
Heh, look at that. Shows how at much attention at least one of us pays
to release notes. :)
-- Lars Viklund | zao_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk