Re: Convenience Methods
Re: Convenience Methods
- Subject: Re: Convenience Methods
- From: Uli Kusterer <email@hidden>
- Date: Thu, 27 Sep 2007 10:04:13 +0200
Am 27.09.2007 um 02:19 schrieb Erik Buck:
Alternatively, Apple could decide to create NSCFImmutableArray or
take other steps to restore true immutability. Apple is
inscrutable! From my perspective, Apple currently has the worst of
both worlds: They have the clutter and complexity of distinctions
between mutable and immutable classes; They don't get any benefits
from immutable classes because they aren't really immutable.
Can you elaborate? I wasn't aware there was any problem with
mutability/immutability and CoreFoundation.
AFAIK the internals of CFString & Co. still know whether they are
mutable or not and implement e.g. the "copy" optimization. NSCFString
may not know, but since it effectively calls through to the CFString
class's vtable (at least that's what I'd expect it to do), mutability
and immutability would still work.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
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