|
Boost : |
From: Christopher Kormanyos (e_float_at_[hidden])
Date: 2022-05-07 08:02:49
> Pursuant of discussion elsewhere:
> Does anyone have any concrete objections to Boost moving to a C++14
baseline?
Yes. I do.(Caveat: But I'll be happy to be over-ruled.)
We recently established that C++/Boost are uniqueinsofar as they provide high-level abstractionson top of the C++ language. This C++ languagecreates optimized, compiled object that is nearenough to the machine to facilitate high-performance.
Along those lines, a lot of clients use Boost/C++with older compilers, not because they cherisholder compilers, but since constraints makethem end up stuck there. These are constraintssuch as legacy customer projects, old compilers,legacy licenses, old embedded compilers, and more.
Boost provides a service.
So I would turn around the question...
How low do we have to go tobe moderately modern while supportingas many clients as possible?
in my experience, people might get stuckaround GCC4.8/C++11 and GCC 5.4/C++11-14.For the first sticky point, I'd like to see C++11in this baseline. I can't imagine anyone really*needing* 14 features to express their LIB(better than with 11). Even though 14 has lotsof bug fixes, the only real key advanced featureis relaxed constexpr constraints anddigit separators.
So somehow, even if there is reticance to do so,I'd like that 11 support. But I wont struggle toohard for it.
Kindest regards for this thread, John and all,Chris
On Friday, May 6, 2022, 10:20:25 AM GMT+2, John Maddock via Boost <boost_at_[hidden]> wrote:
Pursuant of discussion elsewhere:
Does anyone have any concrete objections to Boost moving to a C++14
baseline?
This would mean:
* Library authors can drop and remove all support for pre-C++14
compilers after a suitable deprecation notice in place for say 3 releases.
* The community maintenance team can likewise drop pre-C++14 support
from community maintained / orphan libaries.
* CI tests no longer need report pre-C++14 results.
* From the next release onward, the boost super-project should clearly
announce in our release notes, that C++11 and earlier support may no
longer be available from the start of 2023.
Thoughts?
Thanks, John Maddock.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk