On 4/16/26 12:35, Piyush Anand via Boost wrote:
Hello Boost Community,
I am planning a large-scale migration of a legacy codebase from SourcePro Rogue Wave to Boost.
Due to strict production constraints, we need to continue compiling with -std=c++14 across our environments (SLES 15 SP6 and RHEL 9).
My question:
* Can we consider migrating to BOOST given our project follows C++14 standards ( from long term perspective) * Are older Boost versions (compatible with C++14) still receiving security patches or critical fixes? * If not, what is the recommended strategy for teams that must remain on C++14 for an extended period ?
From older discussions, I understand Boost typically focuses on supporting newer C++ standards rather than maintaining older standard compatibility (e.g., C++03). I would like to confirm the current stance for C++14.
Different Boost libraries support different C++ standards. However, looking at https://www.boost.org/libraries/latest/grid/, it seems that the vast majority support C++14. The only exceptions I see are Cobalt (which is a library for using C++20 coroutines) and MQTT5 (C++17, but only relevant if you want to use the MQTT5 protocol). Some library features may require a later C++ standard, but I'd say that C++14 is still very well supported by Boost. -- Rainer Deyke - rainerd@eldwood.com