4 ms·

Many of these look like great suggestions; however, I am always a little worried when I run into “C/C++”. I realize many of the suggestions in this seem to be f

Many of these look like great suggestions; however, I am always a little worried when I run into “C/C++”. I realize many of the suggestions in this seem to be fairly compatible with both languages (some of them certainly aren't; e.g., see the one on the front-page which is on the topic of exceptions and destructors), but I think it is about time we all accept that they are disparate languages and stop treating them as mostly-interchangable or compatible languages. At the very least, the continued reinforcement of the myth that C++ is “just an extension” that sits on top of C really needs to stop. There is no real benefit from it and it can cause plenty of damage when developers incorrectly assume they have adequate knowledge from one of the two languages to be profficient in the other.

gue5t 11y ago
Agreed. "C/C++" as a term tends to be a crutch for cases where the author hasn't thought about the specifics of how their statement might apply differently to each language (much less the various versions and implementations of their specs) and would rather be vague than wrong (but is often both). "Both C and C++" (for exactly those two) or "C-family languages" (for C, C++, obj-C, at least, and as a more general term overall) are more often what people should be reaching for.