Doing that wouldn't magically use the more efficient equality check though
without recoding NSMutableSet almost entirely, or… you know, using
CFMutableSetRef and providing your own equality function.
Thanks
Tom Davie
if (*ra4 != 0xffc78948) { return false; }
On 29 Aug 2011, at 17:43, Dave Zarzycki wrote:
> Or, your code could subclass NSMutableSet and interpose the methods that add
> to the set. In other words, mentally separate "objects that are equal" from
> "objects that should be in the set". The former is an equality check, the
> latter is a policy decision.
>
> davez
>
>
> On Aug 29, 2011, at 7:37 AM, Thomas Davie wrote:
>
>> Because NSMutableSet does not have the ability to specify a different
>> version of equality – though as Mike Ash pointed out in #macdev, NSHashTable
>> may well be appropriate.
>>
>> Thanks
>>
>> Thomas
>> if (*ra4 != 0xffc78948) { return false; }
>>
>
_______________________________________________
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 arch...@mail-archive.com
