On Mon, Sep 15, 2008 at 1:48 PM, Charles Srstka <[EMAIL PROTECTED]> wrote: > On Sep 15, 2008, at 11:34 AM, Sean McBride wrote: > >> And gcc can catch these kinds of things! >> >> $ gcc-4.2 -framework Cocoa -std=c99 -Wall -Wextra ~/Desktop/test.m >> >> /Users/sean/Desktop/test.m: In function 'main': >> /Users/sean/Desktop/test.m:7: warning: comparison of unsigned expression >>> >>> = 0 is always true >> >> Turn on those compiler warnings! :) > > -Wall yes, but -Wextra can get pretty obnoxious. In my experience, that one > tends to flood you with "unused parameter" warnings every time you have an > IBAction that doesn't use the "sender" parameter, or you have a notification > handler that doesn't use the notification object, or you implement some API > that requires you to implement certain functions or methods that contain > parameters you don't need, etc.
gcc allows you to disable individual warnings. So using "-Wall -Wextra -Wno-unused-parameter" will give you all of the good warnings with none of the annoying unused parameter ones. In practice, this single warning is the only one I've found in the entire set of -Wall -Wextra to do more harm than good. Every other warning they have has, in my experience, been completely legitimate. And -Wextra adds so many more useful warnings that I'd never consider leaving it out. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
