"Everyone" huh
-Werror alone won't help you here because GCC doesn't warn for what it stupidly considers perfectly legitimate use of its extensions. Also you should never ship packages that use -Werror. -Werror is for development only. Otherwise a GCC update *will* break your package.pic.twitter.com/PUrnTt6lNr
-
-
yeah, there is a reason why you have to pass --disable-werror when you build binutils from source. But if your code compiles with -Wall -Wextra and my above flags on both latest gcc and clang there aren't going to be as many UB/readability problems with your code i guess
-
Yeah, all this stuff is great for debug builds. I always use -Wall but I usually wind up with Makefiles set up for abbreviated output (or buildsystems that do the same) that make warnings obvious anyway, and then I fix them when I see them.
- Show replies
New conversation -
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.