Yes, only storing "ones" would work well with NSMutableIndexSet's containsIndex
method. If you didn't get a "hit" you'd know that that position was a "zero."
I was incorrectly thinking of NSMutableIndexSet as an array.
--- On Wed, 9/10/08, Shawn Erickson <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 10, 2008 at 9:18 AM, Joel Norvell wrote:
> > OK. I think I've got it. One could use an
> > increasing sequence of integers, letting evenness and
> > oddness determine the boolean state at any index. That
> > would save a huge amount of "overhead" in this case!
>
> You only need to store the "index" of all the "ones" not need for
> even/odd business. You then walk the index set picking out the ones
> and marking down zeros for those indexes not in the set, etc.
>
> Of course the bit vector that someone suggested earlier is likely a
> better tool for this.
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
