• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: -[NSMutableSet addObject:] Ambiguous Docs: -isEqual: vs. ==
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -[NSMutableSet addObject:] Ambiguous Docs: -isEqual: vs. ==


  • Subject: Re: -[NSMutableSet addObject:] Ambiguous Docs: -isEqual: vs. ==
  • From: Nick Zitzmann <email@hidden>
  • Date: Wed, 15 Oct 2008 18:03:20 -0600


On Oct 15, 2008, at 5:45 PM, Jerry Krinock wrote:

I am assuming therefore assuming "-isEqual:" in writing my code. Someone please let me know if they see any risk in that.


Yes, NSSet and its subclasses use -isEqual:. You should override that, as well as -hash.

Nick Zitzmann
<http://www.chronosnet.com/>

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: -[NSMutableSet addObject:] Ambiguous Docs: -isEqual: vs. ==
      • From: Jerry Krinock <email@hidden>
References: 
 >-[NSMutableSet addObject:] Ambiguous Docs: -isEqual: vs. == (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: NSBezierPath problems, seems to be two bugs
  • Next by Date: tearing my hair out: +(NSSet *)keyPathsForValuesAffectingValueForKey:
  • Previous by thread: -[NSMutableSet addObject:] Ambiguous Docs: -isEqual: vs. ==
  • Next by thread: Re: -[NSMutableSet addObject:] Ambiguous Docs: -isEqual: vs. ==
  • Index(es):
    • Date
    • Thread