me: -Wall
compiler: you got it chief
me: is that all of your warnings?
compiler: lol no, I'm saving 86 more!
me: -Wall -Wextra ?
compiler: still no. all and extra leaves out 70 more aren't I coy?
me: -Wall -Wextra -Wpedantic ?
compiler: stillllll holding back 66 :3
me: -Wall-no-really-this-is-like-juggling-chainsaws-and-I-want-you-to-yell-at-me-for-absolutely-everthing
compiler: unrecognized command-line option
=> More informations about this toot | More toots from cpu@hachyderm.io
@cpu
me: -Weverything
clang: ooh ooh i’ve got like half a dozen mutually contradictory warnings, this’ll be fun! by the way, did you know the standard header locations are scary?!
=> More informations about this toot | More toots from fanf@mendeddrum.org
@fanf 😭
=> More informations about this toot | More toots from cpu@hachyderm.io
@fanf @cpu -Weverything is the technically correct answer. It is also documented to be undesirable most of the time: https://clang.llvm.org/docs/UsersManual.html#enabling-all-diagnostics
=> More informations about this toot | More toots from fay59@tech.lgbt
@fay59 @fanf technically correct unless you're stuck with gcc no?
=> More informations about this toot | More toots from cpu@hachyderm.io
@cpu @fanf yes, I only meant to address that Clang’s -Weverything is good to discover diagnostics, not good to use in production. GCC doesn’t have an equivalent, AFAIK (but if it did, the same caveat would apply)
=> More informations about this toot | More toots from fay59@tech.lgbt This content has been proxied by September (ba2dc).Proxy Information
text/gemini