Re: NSObject Foundation tool memory issue?
Re: NSObject Foundation tool memory issue?
- Subject: Re: NSObject Foundation tool memory issue?
- From: Lee Cullens <email@hidden>
- Date: Thu, 08 Dec 2005 20:40:51 -0500
Thanks Scott, Nick & Niko,
I confused myself, but I believe you helped me undo the
misunderstanding. In this exercise I intentionally used NSMutableArray
(automatic autoreleasePool) to accumulate test cases (my created
objects) which need to be retained either outside of or via autorelease
until I [testObjArray removeObjectAtIndex: i] and the individual test
results are instances of the same same class as the test cases but may
be forgotten as soon as displayed.
The priority (to me in this case) is to manage the test cases in
conjunction with the NSMutableArray object (i.e. via autoreleasePool) so
I just have to reorganize my code to have a local pool in the test
loop. I realize there is a cost to this Nick and will note such
relative to priorities for reference.
I had studied the document you noted Scott. I guess it just really
didn't sink in until I screwed things up and you-all helped me get my
head straight. I like your rant as I had no problems managing memory
directly with objc/Object.h, or even as far back as IBM 360 assembler,
but it's also fun to learn and adopt new techniques :-)
Thanks all for bearing with me and keeping me headed in the right direction,
Lee C
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden