Re: NSTimer or double to int cast (Bug?)
Re: NSTimer or double to int cast (Bug?)
- Subject: Re: NSTimer or double to int cast (Bug?)
- From: Chris Ridd <email@hidden>
- Date: Sat, 11 Jan 2003 15:33:48 +0000
On 11/1/03 2:35 pm, Marco Binder <email@hidden> wrote:
>
I am using the same binary, but compiling it again on the iBook (both
>
have dec devtools and gcc 3.1) doesnt change anything.
>
>
OK, just now I4ve done some comparison and calculation stuff:
>
>
[timer timeInterval]<1.0 return NO on my G4 and YES on my iBook!
>
>
([timer timeInterval]-1.0) * 10000 returns 0.00000 on my G4 and
>
-0.00150 on my iBook!
>
>
>
So the returned timeInterval is NOT equal to the value passed for
>
initialization on all machines. I still consider that to be a bug,
>
altough one with easy workarounds.
>
>
Somehow it seems to be correlated with the machines speed, as Cameron4s
>
600 MHz iBook works as expected (that is: correct), whereas my 500 MHz
>
iBook, my girlfriends 400 MHz G3 iMac and another developers 400 MHz
>
iMac all three show the deviation.
Are all those G3 processors the same? What bit pattern does the double
contain on all machines?
Cheers,
Chris
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.