Re: NSNumber compare: Giving Unexpected Results
Re: NSNumber compare: Giving Unexpected Results
- Subject: Re: NSNumber compare: Giving Unexpected Results
- From: Kyle Sluder <email@hidden>
- Date: Wed, 8 Sep 2010 11:50:30 -0700
On Tue, Sep 7, 2010 at 5:58 PM, Chris Tracewell <email@hidden> wrote:
> I have a category on NSDecimalNumber that seems very straight forward - yet is producing odd results. The code below shows my logging and everything outputs as expected - but the final evaluation does not work. Am I misunderstanding something?
Well, your entire method could be replaced with a oneliner:
- (BOOL)isLessThanZero; {
return [self compare:[NSNumber zero]] == NSOrderedDescending;
}
--Kyle Sluder
_______________________________________________
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