| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
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.This seems straightforward enough:I should have added efficiently. I doubt that indexGreaterThanIndex: is O(1) and thus a bad idea for iterating large index sets, which is also hinted by the documentation for getIndexes:maxCount:inIndexRange:, which says: "Use this method to quickly and efficiently traverse an index set".
Forwards:
unsigned currentIndex = [indexSet firstIndex];
while (currentIndex != NSNotFound)
{
//...
currentIndex = [indexSet indexGreaterThanIndex:currentIndex];
}
| 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>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
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.