On 2005-08-16 16:45, "Nicholas Clark" <[EMAIL PROTECTED]> wrote:
> To me, 1.e5 is not ambiguous. But maybe I've had too much dealing with
> floating point in a previous life.
1e5 is not ambiguous. 1.0e5 is not ambiguous, just overprecise. 1.e5 is
ambiguous.
> I'd find it hard defending a language that treated 1.e5 as a method call.
Guess we shouldn't sign you up for the Ruby Defense League, then?
irb(main):001:0> 1.e5
NoMethodError: undefined method `e5' for 1:Fixnum
from (irb):1
irb(main):002:0>
