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!
--- On Wed, 9/10/08, Todd Blanchard wrote:
> Well, if I read it right, he's using the NSString as a very expensive
> bit vector - only storing 0's and 1's.
>
> If instead of storing a '1' at position n he sticks n into the
> NSMutableIndexSet, it amounts to the same thing.
> He can keep an array of NSMutableIndexSets instead of an
> array of NSStrings.
>
> On Sep 9, 2008, at 11:51 PM, Joel Norvell wrote:
>
> >
> > The values in an NSMutableIndexSet are always sorted, so the order
> > in which they are added is not preserved. Wouldn't that defeat the
> > purpose of the OP's data structure?
> >
_______________________________________________
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]
