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
Show this thread
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.
-
-
This Tweet is unavailable.
-
This is with -Wall, and none of those are going to improve GCC's lack of a useful pointer at the actual problem here.
End of conversation
-
-
-
N. Selection, junior dev: AAAGGG ...
...T!
biogcc: point mutation, fatal errorpic.twitter.com/IT7R41PO4TThanks. 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.