Re: Why can't I name a property `tag'?
Re: Why can't I name a property `tag'?
- Subject: Re: Why can't I name a property `tag'?
- From: "Michael Ash" <email@hidden>
- Date: Thu, 10 Jul 2008 23:34:54 -0400
On Thu, Jul 10, 2008 at 2:17 PM, Brian Stern <email@hidden> wrote:
> So I would add "For best results, you should avoid using any method name
> that is already in use unless its return type and parameters are identical
> with the already existing method."
Certainly true. I find this to be less of a bother simply because
Cocoa naming conventions usually result in a different method name
when you have different parameter types, because of the standard way
that parameters get "named", whereas the return type does not. But
it's not unheard of.
> Obviously there is some potential for new versions of Cocoa to add new
> methods that conflict with your own methods.
This is not much of a concern as long as they're in separate classes.
Your existing binary will continue to function, and any conflicts will
(hopefully!) be noted by the compiler when you recompile, so you can
de-conflict the names at that time.
Mike
_______________________________________________
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