3 ms·
"The languages are in much flux" you meant python and not c/c++ because these aren't in flux No I meant C++. 2011 14882:2011[44] C++11 2014 14882:2014[45] C+
by andrehacker 1y ago
"The languages are in much flux" you meant python and not c/c++ because these aren't in flux
No I meant C++.
2011 14882:2011[44] C++11
2014 14882:2014[45] C++14
2017 14882:2017[46] C++17
2020 14882:2020[47] C++20
2024 14882:2024[17] C++23
That is 4 major language changes in 10 years.
As a S/W manager in an enterprise context having to coordinate upgrades of multi-million LOC codebases for mandated security compliance, C++ is not the silver bullet in handling the version problem that exists in every eco system.
As said, the compilers/linkers allow you to run in compatibility mode so as long as you don't care about the new features (and the company you work for doesn't) then, yes, C/C++ is easier for managing legacy code.
- YZF 1y agoThese are new features. Many of them are part of the library not the language. Generally speaking what you do is enable the new features in your compiler, you don't need to disable that to compile old code. It's not a problem to work on legacy code and use new features for new code either.
- guappa 1y agoI can show you a 2 year old python program that will fail to work on an existing version of python. Can you do that with a gcc version?
- badsectoracula 1y agoAFAIK none of this cause existing code to not work.