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: Guy English <email@hidden>
- Date: Tue, 14 Feb 2006 13:51:51 -0500
On Tuesday, February 14, 2006, at 01:48PM, M. Carlson <email@hidden> wrote:
>On Tue, 14 Feb 2006 18:40:13 Martin Hairer wrote:
>>"on PowerPC based machines the return value is undefined"
>... which begs the question: Why doesn't it / can't it simply return 0 like
>it should?
Because setting the floating point return register to zero on every possible method call takes time. Also it implies that you'd need to save of that float register to the stack more often since it'll be clobbered after every objective-c method call, which takes more time. Anyway - from the new docs it looks like that's what happens on Intel now. But I'm still waiting for my MacBook to arrive. :)
Guy
_______________________________________________
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