3 ms·
cma hit the nail on the head and you dismissed it. Two departments or companies aren't going to use the same subset of C++. Coding standards also evolve over
by alayne 11y ago
cma hit the nail on the head and you dismissed it.
Two departments or companies aren't going to use the same subset of C++.
Coding standards also evolve over time as languages evolve and better ideas about software engineering happen. 2015 C++ is much different than 2000 C++. Unless you always work on greenfield development with coworkers that strictly follow the same standards and C++ subset and you never do any kind of maintenance work, you will need to learn more parts of C++ than you may personally wish to use or learn.
- andrepd 11y agoWhat I mean to say is that that isn't the language's fault. It's up to the users to decide to make use of features they need, and obviously it's their responsibility to live with the headaches a misuse/overuse of C++ may bring. I guess I just don't understand why people consider "too many features" to be a shortcoming.
- alayne 11y agoI'm not arguing about too many features and you know it. Complexity and subtleties in a large language can make it difficult to write correct software.
- pzone 11y agoYes, it is harder to write correct software in C++ than in other languages. But if the project you are working on needs to be written in C++, explicit coding standards and the general project environment can play a huge role in whether it is a lot harder, or just a little bit. I can point to one policy that guarantees safety becomes much easier: prefer modern C++14 idioms whenever possible.