• 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: String Comparison and return values
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: String Comparison and return values


  • Subject: Re: String Comparison and return values
  • From: Shawn Erickson <email@hidden>
  • Date: Tue, 26 May 2009 10:55:12 -0700

On Tue, May 26, 2009 at 9:56 AM, Kirk Kerekes <email@hidden> wrote:
> Consider the pattern:
>
> [[thing description] isEqualToString: someString];
>
> All objects will return a string for description. Whether it is meaningful
> in your terms is a whole other issue.
>
> NSNumber will return a sensible numeric string.
> NSString will return itself.
>
> Generally, property-list objects (other than NSData) will return something
> generically useful in response to -description.

You really shouldn't use the string from -[NSObject description] for
anything other then logging or via the debugger.

You should instead use a common form/representation when doing
comparisons across objects of different classes.

-Shawn
_______________________________________________

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

References: 
 >Re: String Comparison and return values (From: Kirk Kerekes <email@hidden>)

  • Prev by Date: [ANN] CocoaHeads Paris #3 - 27th of May (tomorrow)
  • Next by Date: Re: NSPredicateEditorRowTemplate, NSPopupButton and bindings
  • Previous by thread: Re: String Comparison and return values
  • Next by thread: Core data, bindings and multiple view NIBs
  • Index(es):
    • Date
    • Thread