From: Nobuyoshi Nakada <nobu@...>
Date: 2007-12-28T13:31:31+09:00
Subject: Re: Invalid use of mktime() in Ruby 1.8/1.9 results in incorrect Time objects

Hi,

At Fri, 28 Dec 2007 07:37:46 +0900,
Dirkjan Bussink wrote in [ruby-core:14517]:
> The easiest solution is to simply remove the mktime() call and always  
> use localtime() which exhibits the correct behavior. I've tested this,  
> and this results in the correct behavior.

mktime() and localtime() have different function.  It's
impossible to simply replace the former with the latter.
Could you elaborate?

-- 
Nobu Nakada