Amen. One of the first things I do to any Xcode project I work on is turn on "Treat warnings as errors" in the build settings. For some reason almost all of Obj-C's type-checking errors appear as warnings, and you ignore those at your peril.
VERY good advice. A little self-discipline is good. I admit to previously being very bad about "harmless" warnings. By harmless, I mean the "may not respond to" variety. It's messy, though, and it always rubbed my OCD wrong. ;-)
Hi. I'm Idiot Savant and I have a Warnings problem. I've been clean for about a year now and it gets easier every day ...
< sits down, waits for clapping > -- I.S. _______________________________________________ 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]
