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: Daniel Jalkut <email@hidden>
- Date: Tue, 14 Feb 2006 13:32:31 -0500
More specifically, after closer inspection, it corresponds to the
last value passed as floating point register $f1 to a function.
The nil-messaging "floatValue" expects to have $f1 set by the
objc_msgSend, but it doesn't seem to happen. So the old value of $f1
is used instead.
Daniel
On Feb 14, 2006, at 1:21 PM, Daniel Jalkut wrote:
What's interesting is the "random number" seems to correspond to
the last "real float NSNumber" used.
_______________________________________________
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