Re: NSOperation and NSAutoreleasePool
Re: NSOperation and NSAutoreleasePool
- Subject: Re: NSOperation and NSAutoreleasePool
- From: Kyle Sluder <email@hidden>
- Date: Sat, 7 Mar 2009 02:36:05 -0500
On Sat, Mar 7, 2009 at 1:31 AM, Aaron Wallis <email@hidden> wrote:
> Thanks for pointing that one out, but it wasn't the cause for my problem.
> As for retaining the delegate, originally I wasn't, I just took the advice
> from Roland, but it doesn't break if I don't have it there :D
Just because it doesn't break right here, right now does *not* make it
acceptable or correct behavior.
You have a memory management bug that's causing an object to disappear
and another object to be allocated in its place. This bug is caused
by an apparent lack of understanding of the Cocoa memory management
model. The solution is not to randomly stab retains and releases
around; the solution starts with understanding the model.
I do not mean to sound condescending, but this is a very important
fundamental concept. Especially since you seem to be doing something
drag-and-drop related, which will involve multiple method invocations
spread out across run loop iterations and will therefore be that much
harder to get right.
--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