Re: Initializing a NSMutableString an odd way
Re: Initializing a NSMutableString an odd way
- Subject: Re: Initializing a NSMutableString an odd way
- From: Fritz Anderson <email@hidden>
- Date: Wed, 31 Jul 2013 14:52:45 -0500
On 31 Jul 2013, at 2:28 PM, Vincent Habchi <email@hidden> wrote:
> Thanks to all for answering,
>
>> Why would there be? Your just asking for a mutable copy of an empty string. It should be equivalent to [[NSMutableString alloc] initWithString:@« »]
>
> But much slower I expect, since it creates a NSString, takes a mutable copy, then implicitly releases the constant empty NSString.
NSString literals are baked into the application binary, and couldn't be deallocated if you tried. They are interned, so the code sample at the end of this message prints the same addresses for foo and empty no matter how you use them (even the product of -copy).
> BTW, what’s the difference between [[NSMutableString alloc] init] and [[NSMutableString alloc] initWithString:@“”]?
The latter is redundant.
— F
_______________________________________________
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