On 04/03/2011, at 11:54 AM, Matt Neuburg wrote: > because NSString is a very, very special case. Memory management for strings > is utterly different from memory management for a normal object
Is it? Are you basing this on your observations, or on some documentation? I don't see this though I haven't gone out of my way to look for it. There is no reason I've ever found to treat NSString as a special case, and it doesn't sound right to me that strings are effectively never deallocated, which seems to be what you're implying. That would be a leak of a rather major order, wouldn't it? --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
