4 ms·
Does anyone have a clue as to why GCC's messages have remained so bad for so long?
by rrreese 15y ago
Does anyone have a clue as to why GCC's messages have remained so bad for so long?
- alec 15y agogcc's error messages, especially for C++ templates, got much better in 4.5. They don't have pretty colors, but I didn't find a substantial benefit from clang 2.9's vs gcc 4.5's for C++ development when using both for a week. Note that if you're on a Mac, your system's gcc is likely several years out of date.
- X-Istence 15y agoEven with 4.5 I haven't found the error messages to be nearly as helpful. Also with clang you can easily turn on a way to look for undefined behavior and turn those into warnings/errors which is fantastic and helped me track down a bug BEFORE it caused me huge grief.
- Hemospectrum 15y ago> Note that if you're on a Mac, your system's gcc is likely several years out of date. To be precise: Apple stopped maintaining its GCC branch after the switch to GPL3. The last version available with Apple patches is 4.2.1. There will be no further updates to this branch.
- greyfade 15y agoCheck out [Colorgcc](http://schlueters.de/colorgcc.html http://schlueters.de/colorgcc.html). It helps more than you'd think.
- obiterdictum 15y agoBecause it's hard to add it to the mature infrastructure that was not designed to support it from the beginning. Clang was built from ground up to support good diagnostics.