9 ms·

Huh?! ever seen a c++ project not using any pre-C++17 code?! If it's there, sooner or later you're going to have to debug through it :) Anyway, C++ is nothing

• pjmlp 9y ago
  I wrote C++17, just to hint how one should aim to write proper code as of 2018. At very least, one should be making use of C++11 and whatever the compiler already supports from C++14. Of course, it will take time to move from "C compiled with C++ compiler" to something better, specially in the embedded domain where Assembly and C still rule. The tools are there, and an incremental update into safer code is always better than throwing everything away, and rewrite everything, including the already fixed bugs. The only thing that C++ cannot fight against is the C mentality. That is only possible in languages that lack copy-paste compatibility with C.