4 ms·
Lets be clear... half of your list is from C: -Procedural programming -Structures and enumerations -Text based macros -Low-level memory access And for the ite
by kenjackson 16y ago
Lets be clear... half of your list is from C:
-Procedural programming
-Structures and enumerations
-Text based macros
-Low-level memory access
And for the items they actually added to C to make C++, none of them are all that unusual, save templates (not sure if there is any other language that does it compile time).
IMO, Scala has more parts of the sink in it than C++. The problem with C++ isn't the kitchen sink. It's that its built on a language that isn't meant to hold the things that C++ would like to add to it.
Maybe I'm being pedantic, but when I see "kitchen sink" I have a vision of a lot of features. But frankly C++ isn't all that feature rich. But its the interaction complexity that makes it problematic. This is not a problem of throwing the kitchen sink at it, but rather a design problem.
- hga 16y agoLet's put it this way: do you know of any successful C++ project of serious size that doesn't specify and stick to a subset of the language?
- kenjackson 16y agoSeveral that I've worked on. There were aspects of the language that we avoided, like export, because they weren't implemented. But in general, we didn't have ground rules about features to use or not use. At least not in the past 15 years. Back in '93ish we would be more careful, because the features were still evolving, but by 2002-2003 I don't think we had a lot of issue using the language.