On Jan 9, 2009, at 9:13 AM, Andy Lee wrote:
I haven't checked, but I suspect the compiler chooses the right
thing, since this is only a warning. Maybe someone knows a way to
disable the warning? In Java, I wouldn't be surprised if there were
a way to enable a similar warning.
--Andy
Don't do that - compiler warning exist for reasons: to help prevent
you from writing buggy code.
In this case the warning isn't that the compiler is going to do the
"wrong" thing (since it basically gets to define what is right and
wrong - and it is right), it's that your code (or somebody else's code
who has to later maintain this code) is potentially going to make a
mistake and use "label" when they mean the instance variable, and not
"label" the parameter (and then things will break).
Compiler warning are basically its way of saying "I'm going to do
something that you told me to, but it may not be what you meant, since
what you wrote could be ambiguous or have undefined results".
Fix the warning, don't disable it.
Glenn Andreas gandr...@gandreas.com
<http://www.gandreas.com/> wicked fun!
JSXObjC | the easy way to unite JavaScript and Objective C
_______________________________________________
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
