Re: My bug or Apple's?
Re: My bug or Apple's?
- Subject: Re: My bug or Apple's?
- From: John Stiles <email@hidden>
- Date: Fri, 19 Nov 2004 15:04:32 -0800
Well, as a matter of course, I try to release everything I allocate. At
my work, our allocator code will complain about a memory leak if I
don't.
In this particular case, TSHashTables destroy each of their elements
when they are destroyed, because that's how they were designed. Usually
it's helpful. :)
If I just wanted to leak the images, I could make my Image class'
destructor do nothing, but that seems like an error to me. Yes, in this
particular instance we're quitting anyway, so we don't HAVE to free.
But should I really need to make two separate types of Image
objects--one that frees itself on destruction, and one that
doesn't--just because of this bug? It doesn't seem logical to me.
On Nov 19, 2004, at 2:56 PM, John C. Randolph wrote:
On Nov 11, 2004, at 6:49 PM, John Stiles wrote:
I have an app that attempts to free all its resources during the
shutdown phase.
Come to think of it, if you're about to exit the app, why bother to
release objects individually?
-jcr
John C. Randolph <email@hidden> (408) 974-8819
Sr. Cocoa Software Engineer,
Apple Worldwide Developer Relations
http://developer.apple.com/cocoa/index.html
_______________________________________________
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