One aspect of the article, if I understood correctly, is that with abstraction comes uncertainty about the compilation result.
If you need to be 100% sure about what the compiler will produce you shouldn’t go with a higher level language like C++ and stick with C.
"Orthodox C++" looks like an euphemism and the examples are just taking the ++ out.
I use the language for over 20 years now and I've always been quite happy with the new features provided, especially smart pointers and ownership concepts.
So what exactly is the point?
STL is complex? Yes - keep learning and mastering.
C++ compilers produce unexpected results? Tell me you are a master of x86-assembly and know the performance costs of every kernel function your application uses via the compilers abstractions…
I am a little confused. Is this a compiler for an old C++ version, like 1.0 or is it a complete reworking to better match C syntax? I have only used C++ 17 and up, and am unfamiliar with older versions.
One aspect of the article, if I understood correctly, is that with abstraction comes uncertainty about the compilation result. If you need to be 100% sure about what the compiler will produce you shouldn’t go with a higher level language like C++ and stick with C. "Orthodox C++" looks like an euphemism and the examples are just taking the ++ out. I use the language for over 20 years now and I've always been quite happy with the new features provided, especially smart pointers and ownership concepts. So what exactly is the point? STL is complex? Yes - keep learning and mastering. C++ compilers produce unexpected results? Tell me you are a master of x86-assembly and know the performance costs of every kernel function your application uses via the compilers abstractions…