Re: Incorrect Time#<=> specification

I agree that <=> should only compare two temporal objects of the same class,
which is how the method is currently constructed. My patch for a Temporal
mixin:

http://www.ruby-forum.com/topic/139881#622989

which is currently being considered for inclusion into the Ruby core, allows
developers to write code which reinforces this constraint on comparisons by
using the more domain-specific terms "before" and "after" to compare Times,
Dates, etc. For example, it's conceivable a developer might attempt

some_time <=> 10039483

but they would certainly be much less likely to try

some_time.before? 10039483

because the vocabulary more precisely describes what the program is doing.

That being said,

+1 for Vladimir's patch.

On Feb 1, 2008 9:09 AM, Vladimir Sizikov <[e-mail]> wrote:

> Hi,
>
> Currently (in both, MRI 1.8.6 and 1.9) the docs for Time#<=> state
> that the Time object can
> be compared with Numeric argument:
>
> "Difference由eturns a new time that represents the difference between two
> times,
> or subtracts the given number of seconds in numeric from time."
>
> But this is not what the code does. The code compares only Time instances,
> and returns nil for everything else. I was able to dig up the history
> and it seems,
> that the change was intentional in rev. 3823, with comment:
> " time.c (time_cmp): does not compare with numbers for
>  interchangeability. (ruby-bugs-ja PR#458)"
>
> So it seems that the description should be updated to match the behavior.
>
> Here's the simple patch against 1.8 branch, but similar thing applies
> to trunk too.
>
> Thanks,
>  --Vladimir
>
> P.S. Can somebody tell me where can I find that ruby-bugs-ja PR#458
> online?
>