• 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: NSNumber is completely broken
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSNumber is completely broken


  • Subject: Re: NSNumber is completely broken
  • From: Philippe Mougin <email@hidden>
  • Date: Thu, 26 May 2005 00:41:15 +0200

> I wouldn't say that NSNumber is totally broken based on the
> results that you're seeing. It's just an implementation decision
> that disagrees with an implementation decision that you would make.
> NSNumber still behaves properly according to all the publicly
> documented behaviors.

Well, actually NSNumber is really completely broken.

For example:

[[NSNumber numberWithUnsignedChar:200] isEqualToNumber:[NSNumber numberWithInt:200]]

will return NO (it should return YES of course).

Best,

Philippe Mougin
http://www.fscript.org

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: NSNumber is completely broken
      • From: Bill Cheeseman <email@hidden>
  • Prev by Date: Re: "Validates immediately" validates some time later?
  • Next by Date: -revertToInitialValues not 'taking'
  • Previous by thread: Re: NSNumber is completely broken
  • Next by thread: Re: NSNumber is completely broken
  • Index(es):
    • Date
    • Thread