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

In article <FF85AFA8-EBC4-493D-A61E-63DF6B0E48AF@gmail.com>,
  Dirkjan Bussink <d.bussink@gmail.com> writes:

> FYI: This breaks behavior such as Time.local(2005,2,29), which creates  
> a Time object for March 1st, 2005. I don't know whether this is  
> defined behavior or just a side-effect of the old implementation. I'm  
> fine with the more restrictive behavior, but I don't know how others  
> feel about this.

I see.

Another example:

% TZ=EST5EDT ./ruby -e 'p Time.local(2007,3,11,2,0,0)'  
-e:1:in `local': couldn't generate a time (ArgumentError)
        from -e:1:in `<main>'

An missing time between a standard time to a DST causes an
error.

Hm.
-- 
Tanaka Akira