Clang: gives up (rightly so) after 1 page, but more importantly *starts with the actual problem*. @llvmorg wins again.pic.twitter.com/rvDolP1eSC
Show this thread
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
-
-
-
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 thread
End of conversation
New conversation -
-
-
-Wfatal-errors
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Still, a better output than c++ errors
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
gcc is such a drama queen.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
GCC must be female... way to make a scene out of basically nothing at all !!
-
Dude, gender stereotyping jokes are waaaay passé.
- Show replies
New conversation -
-
-
This is why I use clang when I can ;)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Good ol' GCC. It certainly knows how to make a mountain out of a molehill.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
lvlup when the erroneous character in deep inside nested
#include sThanks. 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.