News for hackers. Stuff that matters.

A comment on Deep C. Parent comment

Re:Deep C by dodedo on Monday October 10, 2011 @09:25PM (#3096655)
I have to work with folks who confuse size_t with int, and as a result they have overflow bugs depending on whether O_LARGEFILE is in use. So yes, I care. Not because printf format strings are terribly important, but because understanding and adhering to the type system is essential to write bug-free software.
[ Parent | on HN ]
Re:Deep C by 0x12 on Tuesday October 11, 2011 @06:59AM (#3098073)
If they get overflow errors then your build process does not have the right warnings enabled/logged.

Suggestion: enable -Wall and treat warnings as errors.

[ Parent | on HN ]
Re:Deep C by dodedo on Tuesday October 11, 2011 @12:45PM (#3099282)
Of course. You and I know they're doing it wrong, however sirclueless suggested above that type correctness is "arcane" and asks if "we would really care" when it comes to type issues in printf format strings.
[ Parent | on HN ]
Re:Deep C by pwaring on Tuesday October 11, 2011 @07:02AM (#3098082)
Handily, gcc has -Werror, which turns all warnings into errors. So -Wall -Wextra -Werror should catch most things.
[ Parent | on HN ]
Re:Deep C by aninteger on Tuesday October 11, 2011 @05:20PM (#3100341)
Except if you're using gcc (mingw) on Windows:

gcc -v shows that it's been configured with --disable-werror

[ Parent | on HN ]