I really think I understand that link, and the only reason I bring up the
retain count is because I know I'm not releasing it too early (cause I don't
release these objects for now).
What I'm afraid is happening is that it's being overwritten somehow and that
when I access the NSNumber object, I get the error. Or possibly something to
do with the threads that I don't understand, but I just don't see it.
On Jan 20, 2008 12:09 AM, I. Savant <email@hidden> wrote:
> > I believe I've got my memory management correct and that my retain
> > counts
> > are good.
> >
> DO. NOT. RELY. ON. RETAIN. COUNT.
>
> I say that so boldly so there is no chance of being unclear. If
> you're blindly basing "correct memory management" on retain count, you
> do not yet understand the memory management mechanism. An object
> instance's retain count is, frankly, none of your business. That's
> between the instance and the system.
>
> > Anyone have an idea?
>
> Yes, a bright one. Read this thoroughly:
>
>
> http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Tasks/MemoryManagementRules.html
>
> Does the entire life cycle of your problem instance follow these
> rules? If your answer is no, there's your problem. If your answer is
> yes, I call bull****. ;-)
>
> --
> I.S.
>
>
>
>
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
