2 ms·
Also, it's not always a problem of being able to work with other. Having a standard also means that other compilers will compile your C++ code. We're not talki
by jokoon 11y ago
Also, it's not always a problem of being able to work with other. Having a standard also means that other compilers will compile your C++ code.
We're not talking about a language, we're talking about a programming language, and standards and compilers are the only metrics which make that language "talked" by others.
- michaelmior 11y agoIsn't a programming language both? Sure the goal is arguably to communicate some process for the computer to perform in a machine-readable way. But I can easily write two valid semantically equivalent programs which produce equivalent code when fed to a standards compliant compiler. However, one of these programs may be much more readable to a human because it follows an established set of coding practices. Perhaps a better word that standards would be "conventions" but either way, most programs also need to be read by humans at some point.
- Aeolos 11y ago> Having a standard also means that other compilers will compile your C++ code. As someone maintaining code that must run on VS2012, VS2013, VS2015, GCC 4.7+, clang 3.5+, on both x86 and x86_64, I chuckled hard at your comment. Let's just say that I'm looking forward to moving on with my career in a few months. Hopefully to something that doesn't involve maintaining C++ code.