2 ms·
> When you switch between two projects writen in C++, it is almost as if they were using a different language. I strongly disagree. This may have been the case
by jcelerier 8y ago
> When you switch between two projects writen in C++, it is almost as if they were using a different language.
I strongly disagree. This may have been the case 20 years ago, but most current projects use C++, not some weird -fno-rtti -no-stdinc -fno-whatever sub-language. Maybe they don't use all the features of the standard library, but which project in Java or Python would ?
- tomjakubowski 8y agoWell, to me it's like the way Shakespeare, e e cummings, and Kool Keith all write in the same language. Context switching between working on work codebase, Chromium code base, and various third party C++ codebases is a headache as much for their basic differences in coding style (use of whitespace, capitalization, naming, etc.) as for their wildly varying build/metabuild processes. And of course, each implements and then extensively uses their own library features like reference-counted pointers, managed GC pointers, collection data structures, iterator-like abstractions, etc.
- nescoiquid 8y ago> their wildly varying build/metabuild processes. Boost? I'm sure there's good reason for the -- sui generis -- build system. Always been too underwater to spend much time wondering about why that's a yak I'm shaving.