Thanks for looking into that Vincent.
My 2 cents, for what it is worth:
- NEVER use floating point for equality checks. Ever.
Not only is the precision misleading (Radix 2 - isms/ etc.), but 32 vs. 64
... etc. get in the way, quite often, in fact
- If NSDate in particular, "always use NSDate
> My conclusions,
> - 0.7 and 0.9 fix return the correct time now, 0.9 fix can't do necessary
> time arithmetic
> - Ruby Time.to_f is broken in all 3 versions
> - Bignum.to_f is broken in all 3 versions
> - I believe the to_f method is behind all of these problems but i haven't had
> time to find
I suppose this begs the question: Does anyone really *require* 32 bit support
for MacRuby at this point? SnowLeopard is already the minimum supported
config, and the only Intel 32 bit-only platforms (very early MacBook and Mac
Mini configurations) are several years old now. I don't want to so
> 1. Modified the Valid Archetectures to "i386 x86_64"
There's a simple way to run macruby (or any other program) on the
command line in 32 bits: just add "arch -i386" before the name of the
program to execute:
$ macruby -v
MacRuby 0.9 (ruby 1.9.2) [universal-darwin10.0, x86_64]
$ arch -i386 macru
