> But that doesn't mean it is a bad language.
It is when programmers blindly use OOP as a Silver Bullet (TM) and then wonder WTF they run into all sorts of performance problems ...
"Pitfalls of Object Oriented Programming"
* http://research.scee.net/files...
I'm sorry but the C++ committee has their head up their @$$es for *practical* matters:
* Standardized Name Mangling?
* Standardized ABI so compiler A can call code compiled with compiler B
* Standardized error messages
* Standardized pragmas to enable/disable warnings for unused variables
* Standardized forced inline, never inilne
* A consistent grammar between forward declarations and function definitions to make it easier to copy/paste
void foo(); // semi-colon required
void foo(); // semi-colon is error
{
}
* Multi-column debugging instead of the archaic line debugging
foo(); bar(); qaz(); // try setting a breakpoint on bar .. most debuggers only support line debugging?!
Gee, who would ever want that!
Yeah, lets ignore real world issues for the past 20 years and keep adding CRAP onto the language ...
"A Proposal to Add 2D Graphics Rendering and Display to C++"
* http://www.open-std.org/jtc1/s...
For high performance games, most of the C++ features are *ignored*
"CppCon 2014: Nicolas Fleury "C++ in Huge AAA Games"
* https://www.youtube.com/watch?...