Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Iterating NSSet (was Re: My new framwork)

On 4. Mar 2004, at 0:48, mmalcolm crawford wrote:

NSIndexSet internally caches last-accesses, allowing such enumeration (forwards or backwards) to happen very efficiently. The code snippet above should be good enough for most uses. A reason to switch to the get... variant is to avoid the message-sending overhead of the loop, in case that becomes an issue.

That would certainly make a nice addition to the documentation! :) Generally running time for many other methods would, but I'm not the only one who have previously requested this...

On a related note, does NSImage cache the decoded image returned from imageNamed:? I can see that I get the same pointer back, even when I do not retain the result, but I'd rather not rely on caching, if not said so in the docs (but would love to get rid of the 10+ ivars for all the small images used by my custom view plus all the release methods in dealloc).
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >My new framwork (From: April Gendill <email@hidden>)
 >Re: My new framwork (From: John Randolph <email@hidden>)
 >Re: My new framwork (From: Allan Odgaard <email@hidden>)
 >Re: My new framwork (From: mmalcolm crawford <email@hidden>)
 >Re: My new framwork (From: Allan Odgaard <email@hidden>)
 >Iterating NSSet (was Re: My new framwork) (From: mmalcolm crawford <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.