On Mar 25, 2008, at 9:26 AM, James Hober wrote:
Do you write the dealloc anyway? Just wondering what others do.
Personally I still write a dealloc method in a class for an object
that I keep around for the life of the app. Then I preface it with
a self-amusing comment:
//actually
On Mar 25, 2008, at 9:44 AM, j o a r wrote:
I wouldn't recommend doing that. I'd suggest using something like
this:
- (void) dealloc
{
NSAssert(FALSE, @Singleton objects should never be released);
[super dealloc];
}
This communicates better what your intention is, and also
On Mar 25, 2008, at 3:19 PM, James Hober wrote:
On the other hand, the documentation for dealloc says:
Note that when an application terminates, objects may not be sent a
dealloc message since the process’s memory is automatically cleared
on exit—it is more efficient simply to allow the
until all steps are completed
in Download. Thus call [myDownload cancel] and wait for
Notification say DownloadCanceled. Only then deallocate object.
Is there any way to figure out when user initiated quit
application? How to delay it?
I think there should be something pretty much similar
