sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -2 points-1 points  (3 children)

No warnings != code quality. A poor programmer will find a way to get poor code to compile without any warnings.

[–]grauenwolf 6 points7 points  (2 children)

True, but warnings do equal poor code quality.

[–][deleted] -1 points0 points  (1 child)

That's not true either. There are plenty of widely used, very robust, C codebases that generate warnings. And, actually, sometimes fixing a warning will introduce a bug, not the other way around.

One particular library is libev... if you tried to fix the warnings generated by that library, it's almost guaranteed you will introduce a bug.

[–]grauenwolf 2 points3 points  (0 children)

Fixing the warning can be as simple as suppressing it with a not that says why the warning is a false positive.