[jcelerier]

The average C++ codebase isn't from the 90s. On all the recent c++ polls the average language revision used is between c++14 and 17.

Besides I'm pretty confident that there are more new c++ projects created daily in 2021 than monthly at the peak of the 90s c++ craze - just on GitHub, 6/7% of C++ repos means a few million recent C++ repos.

[dagw]

I've worked on several code bases that nominally are C++11 or 14. However they still contain a lot of code written by people still coding like it's the 90s.

[varjag]

What does it have to do with what we are discussing?

[jcelerier]

we are discussing the sentence "The average C++ code base has as many segfaults than the average C code base."

__s and you said "You were using C++ >= 11 in 90s/00s?" to which I answered that this was not the point, because the average C++ code base isn't from the 90s/00s.

[secondcoming]

> On all the recent c++ polls the average language revision used is between c++14 and 17.

Polls of hobbyist coders, or software houses? I would be surprised if most software houses migrated to C++17 yet. Tensorflow is stuck on C++03 I think.

[jcelerier]

TF is at least C++11 from the first header I opened in the repo: https://github.com/tensorflow/tensorflow/blob/master/tensorf...

I'm referring to e.g. the Jetbrains and cppcon polls.

https://blog.jetbrains.com/clion/2020/06/dev-eco-cpp-2020/

https://youtu.be/JYzDpXI-vWI?t=137

[secondcoming]

Last time I used it there was faff around having to define __GLIBCXX_USE_CXX11_ABI=0

[jcelerier]

it does not mean that you're not using C++11. This macro is just a compatibility flag for your code to work on old linux distros that provide a C++11 compiler but did not want to rebuild their whole archive. It mainly means that std::string is implemented with copy-on-write instead of small buffer optimization.