Boost logo

Boost :

Subject: Re: [boost] boost.test regression or behavior change (was Re: Boost.lockfree)
From: Bjorn Reese (breese_at_[hidden])
Date: 2015-10-04 07:09:09


On 10/04/2015 12:18 PM, Gennadiy Rozental wrote:

> Sooner rather than later we should have this discussion and setup timeline.
> IMO it had very little sense to continue to maintain c++03 workarounds.
> Boost code should be an example how modern c++ libraries should look like.
> And c++03 compatibility is directly in a way of this goal.

You appear to have missed the many discussions on this topic.

While Boost started out to design cutting-edge libraries, it has been
caught by its own success. Today there is a large user-base that still
uses C++03, and that are unlikely to upgrade in the foreseeable future.

Therefore, the current consensus is that existing libraries should not
increase their standards requirements. New libraries are free to decide
their standards requirements (although it will probably be questioned
during a formal review.)

That means that you have two options:

   1. Add a new C++11-only test library (like Boost.Coroutine2.)
   2. Maintain both a C++03 and C++11 API within the same library.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk