C coders who didn't code particularly well in C being unleashed on C++. I've seen numerous examples of legacy code done by people with that background which ends up with huge classes that do lots of different things. Or using polymorphism only to needlessly break it a few lines later. Or sprinkling mallocs in code. And so on...
Granted the problem isn't necessarily that they were C coders beforehand, but at least part of it is that they think functionally and with a C-mindset instead of a C++ one and didn't spend the time switching that mindset before starting to write C++. For what it's worth I agree that C++ coders should learn C first, for the same reason that I think any C-style OO language developer should have a grounding in C++ first.
Register
The real problem is...
C coders who didn't code particularly well in C being unleashed on C++. I've seen numerous examples of legacy code done by people with that background which ends up with huge classes that do lots of different things. Or using polymorphism only to needlessly break it a few lines later. Or sprinkling mallocs in code. And so on...
Granted the problem isn't necessarily that they were C coders beforehand, but at least part of it is that they think functionally and with a C-mindset instead of a C++ one and didn't spend the time switching that mindset before starting to write C++. For what it's worth I agree that C++ coders should learn C first, for the same reason that I think any C-style OO language developer should have a grounding in C++ first.