Support status for C++03 (std=c++03) in Boost [Version] on RHEL 9
Hello Boost Community, I am currently planning a large-scale migration of a legacy codebase from SourcePro Rogue Wave to Boost. Due to strict production requirements, we must maintain the -std=c++03 flag across environments: RedHat 9 (GCC 5.x) My Question: Is there any version of Boost, which can be considered the "Long Term Support" equivalent for C++03, for which Boost also release latest patch or security vulnerabilities or actively maintain that version? From older post/blogs, it seems Boost does not manage c++03 standard and provide support of latest standard of c++ only i.e. C++14 and so on. Thanks And Regards, Piyush
Piyush Anand wrote:
Hello Boost Community,
I am currently planning a large-scale migration of a legacy codebase from SourcePro Rogue Wave to Boost. Due to strict production requirements, we must maintain the -std=c++03 flag across environments: RedHat 9 (GCC 5.x)
My Question: Is there any version of Boost, which can be considered the "Long Term Support" equivalent for C++03, for which Boost also release latest patch or security vulnerabilities or actively maintain that version?
In short, no. We no longer support C++03 and we don't maintain old versions.
From older post/blogs, it seems Boost does not manage c++03 standard and provide support of latest standard of c++ only i.e. C++14 and so on.
The prevailing minimum requirement is still C++11, and GCC 5 with -std=c++11 is still supported by the majority of libraries. -std=c++03 is not, however.
I believe 1.83 was the last version that had any substantial C++03 support, but there were already many libraries in there that didn't. There haven't been any security backports to that, but I'm not aware of any security fixes in any of the libraries, so you may be okay there. Tom On Wed, Mar 25, 2026 at 6:07 AM Piyush Anand via Boost < boost@lists.boost.org> wrote:
Hello Boost Community,
I am currently planning a large-scale migration of a legacy codebase from SourcePro Rogue Wave to Boost. Due to strict production requirements, we must maintain the -std=c++03 flag across environments: RedHat 9 (GCC 5.x)
My Question: Is there any version of Boost, which can be considered the "Long Term Support" equivalent for C++03, for which Boost also release latest patch or security vulnerabilities or actively maintain that version?
From older post/blogs, it seems Boost does not manage c++03 standard and provide support of latest standard of c++ only i.e. C++14 and so on.
Thanks And Regards, Piyush _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/OIHVCYV6...
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. Any guidance or best practices would be greatly appreciated. Thanks and regards, Piyush
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
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.
OpenMethod requires C++17. J-L
On 4/16/26 17:45, Jean-Louis Leroy via Boost wrote:
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.
OpenMethod requires C++17.
Yeah, I missed that one. And Parser, and Redis. Still a small minority of libraries. -- Rainer Deyke - rainerd@eldwood.com
participants (5)
-
Jean-Louis Leroy -
Peter Dimov -
Piyush Anand -
Rainer Deyke -
Tom Kent