GCC is trying to tell me "you accidentally typed an 'o' at the top of your C file'. This is the first 4 pages. There were 3 more.pic.twitter.com/S4DdnWU5a4
Show this thread
Clang: gives up (rightly so) after 1 page, but more importantly *starts with the actual problem*. @llvmorg wins again.pic.twitter.com/rvDolP1eSC
-
-
Guys, stop suggesting -Wfatal-errors. GCC's first error message is useless. Only getting the first error is worse than getting 7 pages of crap, because at least with the 7 pages if you've seen this kind of mistake causing spew in the past you can guess the likely cause.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
their error messages have always been better than gcc's
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Both gcc and clang support stopping compilation after the first error via -Wfatal-errors; helps tremendously for reducing error spam like that, assuming the first error message is intelligible anyway ;)
-
Too bad GCC's first error is useless for diagnosing the actual problem. In GCC's case having 7 pages of errors is better than a single error; it makes it obvious *if you're used to this kind of nonsense* that the problem is something silly at the top of the file.
End of conversation
New conversation -
-
-
-Wfatal-error should kill it on the first error. I have a feeling msvc also does this
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
try with -Wfatal-errors
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
holy crap! I never seen so many errors over such a little msitake!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
What’s VCC’s behavior out of curiosity?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.