> I highly recommend treating warnings as errors. (There's a checkbox for that > in the build settings.) There are too many types of serious issues that the > compiler only treats as warnings — the most serious one is the Obj-C > 'unrecognized selector' warning. If I misspell a method name, that's a > guaranteed exception at runtime, so I want to fix it right away.
Indeed - a similar situation can arise where the compiler is forced to guess the type of an argument to the said method, often leading to its corruption at runtime. That's a fun one to debug. _______________________________________________ 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 arch...@mail-archive.com
