Re: always show warnings?
Re: always show warnings?
- Subject: Re: always show warnings?
- From: Dave Keck <email@hidden>
- Date: Mon, 8 Feb 2010 07:51:47 -1000
> 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 (email@hidden)
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:
This email sent to email@hidden