Re: NSString's "mutableCopy" creating a leak?
Re: NSString's "mutableCopy" creating a leak?
- Subject: Re: NSString's "mutableCopy" creating a leak?
- From: "I. Savant" <email@hidden>
- Date: Wed, 1 Oct 2008 16:30:51 -0400
On Wed, Oct 1, 2008 at 4:16 PM, Christopher J Kemsley <email@hidden> wrote:
> I was not aware that I shouldn't explicitly call a dealloc... Why not?
> Replacing it with a "release" in the object made that leak go away, but I
> still don't understand why I can't dealloc it.
The link I sent you earlier is part of a bigger guide that details
this and everything else you should know about memory* management in
Cocoa:
http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/MemoryMgmt.html
You owe it to yourself (and the list ;-)) to study it closely; it's
a fundamental concept.
--
I.S.
* - I ALMOST hit send with this spelled as 'mamory management' ... a
little too close to 'mammary management' if you ask me. Oops. ;-)
_______________________________________________
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