> For as long as I can remember, I have heard people say C/C++ when referring to a project written in C and or C++. A lot of programming/developer jobs also ref

> For as long as I can remember, I have heard people say C/C++ when referring to a project written in C and or C++. A lot of programming/developer jobs also refer to C/C++ when they need a programmer who knows either C or C++. To most people who have never touched C or C++ this might not seem like a big deal. However, the problem is that when people say this term (C/C++) they make it seem like C and C++ are similar or closely related programming languages. That is not true. The post answers itself right off the top. They're close enough that finding someone with experience in either is potentially qualified to be considered for a role. For someone who specializes in only C or C++, they're very different. In the context of programming languages on the whole, experience in one often means a lot of context to using the other. If you have a problem with "C/C++", I'd even have a problem with saying C++ since usages can vary so widely. I learned K&R C, then some MSVC++ with MFC/ActiveX/COM, some OS/2 SOM/IDL C++, then more ANSI C and later C++. But now the modern C++ I sometimes see is quite different. No one uses all new features but if they did, it seems like a different language. We still call it all C++. And to me C is still an improper subset. Edit: I also sometimes write F#/OCaml, is that wrong? Depends on the context.