This is a common complaint about C++, as if the other languages were any better in this regard.
Java 11, C# 8, Python 3.7, Fortran 2018, F# 4.5,.... try to write in a way that everyone will agree with, or do language quiz to see what which one gets right.
Sure there is C that looks so simple, who gets right all the ISO C changes between C89, C90, C11, C17, UB and compiler specific extensions/issues without having to look into the books?
Re:C++ Core Coroutines Proposal [pdf]
by gpderetta on Friday September 21, 2018 @06:01AM
(#18038495)
> I spent a decade watching C++ painfully slowly add more advanced template support and... well, that's about it. After a million iterations of "for (mylisttype::const_iterator i ..." they finally added ranged for loops.
C++ was first standardized in '98. Nothing happened for more 10 year (in particular no new advanced template support) unless you count the very minor bug fixes in C++03. The next revision, C++11, added ranged for loops.
Re:C++ Core Coroutines Proposal [pdf]
by hfdgiutdryg on Friday September 21, 2018 @08:51AM
(#18039293)
Compilers don't strictly adhere to standards, and I'm far more concerned with things like whether my compiler crashes, how godawful the error messages are, and whether the bundled STL even functions reliably.
Haha, you're too crusty to be listened to!
Yeah, you're right. In some respects, things haven't changed.
The rate of change seems to be increasing. This is initially a bit shocking until I remember that every single job I had was like using a completely different language because, even ten years ago, every shop used a different subset of C++ and STL!
Add all you want to the language, it's all going to devolve into code-review infighting the same way it did in 2008.