Re: ivar name clashes with gcc3
Re: ivar name clashes with gcc3
- Subject: Re: ivar name clashes with gcc3
- From: Camillo Lugaresi <email@hidden>
- Date: Thu, 9 Feb 2006 22:51:47 +0100
On 08/feb/06, at 23:14, Ricky Sharp wrote:
Finally, other reasons why I went "nuts" in renaming everything:
* Wanted to guarantee uniqueness of names used for custom
bindings. My controls often use inherited bindings, but I
sometimes need to provide my own implementation. Having _II allows
me uniqueness and also it's easy to see at-a-glance what are my
bindings vs. those provided (as seen in the bindings inspector in IB).
* There's a very small chance that some of my code may be released
for the consumption of other developers. I wanted to ensure no
collisions would exist with their code.
What I've effectively done is guarantee all my code lives within
its own "namespace".
Interesting. This approach has obvious benefits, and I wonder why
Apple doesn't seem to encourage it at all (in sample code,
documentation etc.). Is there a list of best practices for dealing
with namespace problems in Objective-C? (apart from those two-letter
prefixes everybody puts on class names...)
Camillo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden