Hacker News new | ask | show | jobs
by thrwaeasddsaf 1867 days ago
GCC also copied clang's excessive diagnostics and I'm seriously thinking of making a fork just to strip them out. I doubt the developers would accept a patch that implements --stfu.
2 comments

Every change breaks someone's workflow. But you are the closest I've seen to the person complaining here - https://xkcd.com/1172/
Yeah. It's funny how back in the day people used to make fun of excessively long compiler errors involving templates.

Now everyone seems to praise the compiler barfing three screenfuls of text and code and explaining the include hierarchy of my project and expanding all the macros and making bogus suggestions because I mistyped a variable name.

It's gotten to the point where locating the actual error message is literally more work than fixing the code. It doesn't help that this interferes with navigation in emacs and trying to jump to next error instead takes you to the next #include line gcc wants you to learn about.

Does -fdiagnostics-plain-output not do what you want?

    $ cc -fdiagnostics-plain-output c.c
    cc: error: unrecognized command-line option ‘-fdiagnostics-plain-output’
It's new in gcc 11.1