Re: NSTimer never being deallocated
Re: NSTimer never being deallocated
- Subject: Re: NSTimer never being deallocated
- From: Tobias Jordan <email@hidden>
- Date: Sun, 14 Mar 2010 22:13:18 +0100
If these cachings don't result in a huge memory leak (which they
obviously don't do) I am fine with it. :-)
On Mar 14, 2010, at 10:09 PM, Steve Christensen wrote:
On Mar 13, 2010, at 10:57 AM, Tobias Jordan wrote:
What made me think it is a bug was actually only the fact that
instruments told me the object is always still alive and the
'missing' note in the documentations that tell me I don't need to
release it because of some caching techniques.
Whether or not caching is happening behind the scenes is an
implementation detail, not something that should need to be
specifically called out in the documentation if it's not germane to
the published behavior. Obviously there are cases where it's
specifically called out when there is a clear benefit. For example, +
[NSImage imageNamed:] maintains a cache for reusable images to
minimize the memory footprint and image load times.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden