Re: assign property behaves differently from simple instance variable???
Re: assign property behaves differently from simple instance variable???
- Subject: Re: assign property behaves differently from simple instance variable???
- From: Kyle Sluder <email@hidden>
- Date: Tue, 14 Dec 2010 10:28:03 -0800
On Dec 14, 2010, at 9:01 AM, Matt Neuburg <email@hidden> wrote:
>
> Doesn't anyone besides me want to evince any outrage that this can happen? I mean, sheesh, if I wanted to live in a world where the namespace was polluted with secret undocumented terminology I could collide with accidentally, I could use AppleScript. m.
The only thing that infuriates me more than the time spent hunting down name collisions with private APIs is the insistence from some parties that ObjC namespaces are a solution in search of a problem.
In a world with KVC/KVO where prefixing method names to ensure uniqueness is no longer feasible, Apple needs to deliver namespaces for ObjC. Hacks like "private API begins with underscore" aren't enough to deal with public/private namespace collisions or multiple similarly-named classes being loaded dynamically into the same process.
The only real way to get that point across is to keep filing Radars when situations like this arise.
--Kyle Sluder_______________________________________________
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