Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
- Subject: Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
- From: Andy Armstrong <email@hidden>
- Date: Tue, 14 Feb 2006 19:07:26 +0000
On 14 Feb 2006, at 18:21, Daniel Jalkut wrote:
Interesting. I just took your snippet and also reproduced funny
behavior (identical config to yours, incidentally).
What's interesting is the "random number" seems to correspond to
the last "real float NSNumber" used.
For instance:
float fval=0.0;
NSNumber *aNumber=nil;
NSNumber *secondNumber = [NSNumber numberWithFloat:0.5];
fval=[aNumber floatValue];
NSLog(@"fval is %f",fval);
fval is always 0.5.
It sounds like a bug to me. Maybe somebody from Apple will have an
opinion about this.
I presume - without having looked at generated code - that the
floating point register that would be used to return a result is not
being initialised in the case where the pointer is nil - so you're
seeing whatever value was previously in that register.
--
Andy Armstrong, hexten.net
_______________________________________________
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