I wonder how many total person-years of time has been wasted debugging errors arising from implicit int conversions in C.
-
-
Replying to @pcwalton
Or from porting software to 64 bits and debugging errors due to 'long' doubling its size.
1 reply 0 retweets 0 likes -
Replying to @mathausmendel @pcwalton
One legacy codebase had extern prototypes missing in some places. Pointers getting sign-extended are quite a sign, I should say
1 reply 0 retweets 1 like -
s/a sign/a sight/
1 reply 0 retweets 0 likes -
would be nice if more compilers actually enforced the missing-prototypes thing (GCC has an option for this, MSVC doesn't do it at all, ...).
1 reply 0 retweets 3 likes -
There's no easy solution when migrating legacy code from another compiler and platform because" fixing" any warning can break everything
2 replies 0 retweets 0 likes -
Replying to @astarasikov @cr88192 and
This warning is _always_ a serious bug. It should just be an error.
4 replies 0 retweets 2 likes -
Replying to @RichFelker @astarasikov and
-Werror=implicit-function-declaration should be a default, damnit.
1 reply 1 retweet 7 likes -
Replying to @bofh453 @RichFelker and
Is it not with -std=c99 and -std=c11, the latter of which is default for recent GCC and Clang?
1 reply 0 retweets 0 likes
No, sadly it's not.
-
-
Replying to @RichFelker @bofh453 and
I guess my brain auto-promotes that warning to an error. I'd use -Werror more but too many m4 scripts aren't ISO
0 replies 0 retweets 0 likesThanks. 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.