Please avoid use of "C/C++"; C and C++ are distinct languages

[anthonywilliams]

There is no language "C/C++". The continued use of such a term confuses people and propagates the misconception that there is. C and C++ are different languages with different ISO standards and different committees.

If you mean "C or C++", say that. If you mean "C and C++", say that. If you mean something else, please clarify appropriately.

A "technical note" on C++98 to C++20 should not contain such an incorrect term.

[burlachenkok]

Hi, thanks for your feedback.

The continued use of such a term confuses people and propagates the misconception that there is.
If you mean "C or C++", say that

Maybe it's better not to use a slash in the text and instead use English "or", but at least originally, I used the term C/C++ to mean "or", but there is a lot of confusion. I agree:

• C or C++
• C and C++
• C++ part which C compatible

If you mean "C or C++", say that. If you mean "C and C++", say that.

There is a Glossary section at the beginning. And this is precisely the first thing in Glossary:
https://github.com/burlachenkok/CPP_from_1998_to_2020/blob/main/Cpp-Technical-Note.md#glossary

C and C++ are different languages

Sure. By the way, some differences are here:

https://github.com/burlachenkok/CPP_from_1998_to_2020/blob/main/Cpp-Technical-Note.md#technical-differences-between-c-and-c

And in fact, there is a technical document from the committee with more differences.

@ujos can you please share this excellent document again (in this thread)?

p.s. Once in the future in the next pass, I will take this in mind.

Thank you one more time !!!

[ujos]

@ujos can you please share this excellent document again (in this thread)?

Sorry, I do not remember which one? @burlachenkok

[burlachenkok]

It's the official document from IEEE that enumerates the difference between C and C++. In this list, it was 40-60 bullet points. @ujos

[ujos]

Sorry, I do not remember where did I get it from. If you could give me a hint, how did you receive it from me, I can find it then.

[burlachenkok]

@ujos no problem. Thanks.

[burlachenkok]

Dear @anthonywilliams thank you very much for pointing this out.

I totally agree with you regarding using naming, and you are right. During the next pass, I will replace C/C++ with "C and C++" or "C" or "C++" depending on context.

Unfortunately, there are plenty of places in the text that uses "C/C++" already.