Re[4]: NSTableView and memory management problem.
Re[4]: NSTableView and memory management problem.
- Subject: Re[4]: NSTableView and memory management problem.
- From: Dmitry Basko <email@hidden>
- Date: Mon, 28 Mar 2005 23:54:15 +0200
Hello,
SK> Objects will often retain+autorelease in a getter, or autorelease in a
SK> dealloc, an object that they own. This has nothing to do with your
SK> (non)use of autorelease, it's just implementation details of the class
SK> you are using. Maybe NSArray autoreleases its objects on dealloc, maybe
SK> not. Maybe it's NSCell.
Steven, of course you are right, thank you for this valuable explanation. It
makes me sad (I mean if I'm given a chance to determine the behaivior
of a certain object, like sending it "autorelease" message or merely
destroying it, I would _not_ expect that later my object will be
anyway, stored somewhere for a while, and wait for its turn to be
silently destroyed).
SK> I don't know, it's probably not documented and
SK> you generally shouldn't care. In your specific case, this is bad news
SK> but if you want to do something about it you'll have to do some serious
SK> tweaking, I'm afraid... Check the state of the autoreleasepool right
SK> before the big Pop to see what's in there and you might be able to
SK> customize the behavior of the framework classes concerned.
Will try, although this is not clear how I can check this pool, which
is a part of the _internal_ implementation of the certain class. Need
to read some more documentation.
Best regards,
Dmitry Basko
_______________________________________________
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