From: Tanaka Akira <akr@...>
Date: 2007-12-28T17:42:51+09:00
Subject: Re: Invalid use of mktime() in Ruby 1.8/1.9 results in incorrect Time objects

In article <945DBEDA-10F1-40D0-AF7E-CF82EFF627AC@gmail.com>,
  Dirkjan Bussink <d.bussink@gmail.com> writes:

> Hmm, thats not good. I've updated it and afaik it has the exact same  
> behavior, except that it explicitly throws an ArgumentError if a check  
> with localtime() fails.

I already modified time.c.  Check the latest trunk.
-- 
Tanaka Akira