5 ms·
Religion and the garbage code C++ compilers produces, incomprehensible error message, unstable tooling, and very long compilation times.
by uecker 1y ago
Religion and the garbage code C++ compilers produces, incomprehensible error message, unstable tooling, and very long compilation times.
- simonask 1y agoWhat year is it, 1998? Am I going crazy? I think you're making some extraordinary claims. I'd love to see some receipts. :-)
- uecker 1y agoWhat specific claim do you think is extraordinary: That embedded programmers still often use C, that compilation times for C++ are often very long, that the languages is less stable than C, or that code produced by C++ can be worse?
- simonask 1y agoEspecially the last claim seems (that code generation for C++ is worse). It's the same compiler backend in all major compilers. Do you have any examples?
- throw-qqqqq 1y agoPurely guessing, but the "unstable tooling" could perhaps refer to the fact that C++ as a language has evolved a lot. I have had trouble compiling older C++ code bases with newer compilers, even when specifying C++98 as source standard. I gave up trying to get Scott McPeak's Elkhound C++ parser to compile, last I had to attempt it. C is a bit more forgiving on that topic (it hasn't changed as much, for better or worse).
- pjmlp 1y agoI assume you are not using GCC or clang for compiling C code, given that are garbage compilers written in C++. Still using tcc, or stuck in GCC 5 ?
- uecker 1y agoGCC was written in C but changed to C++ later. A lot of the code still looks a lot like C. And as a contributor, I would much prefer it was purely C (and compilation times for GCC itself are a pain - although I think this is not because of C++ but because some files grew to big and some refactoring would be in order)
- pjmlp 1y agoDoesn't the change the fact that by now being written in C++, generates garbage code, as per your own words, thus unsuitable for consumption in C projects.