Hamish Allan wrote:
On Mon, Jun 16, 2008 at 1:39 AM, James W. Walker <[EMAIL PROTECTED]> wrote:
No, the controller does not keep a reference to the task. Why would it need
to do that in order to "keep it alive"?
Because that's how memory management works. *Something* needs to keep
a reference to your NSTask, otherwise your program is leaking memory
(unless you're using garbage collection, in which case your task will
simply disappear at some indeterminate point).
I mentioned in my original post that I'm using a wrapper around NSTask.
The wrapper has a reference to the NSTask, and the wrapper manages
itself. As I mentioned in a previous reply to you, I did take care to
release things at the appropriate times, so there is no leak.
Jens Alfke opined that it can be confusing for an object to manage its
own lifespan, but I do not find it so. And I'm not planning on using
garbage collection, at least in my current project.
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________
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 [EMAIL PROTECTED]
