From: Wes Gamble <weyus@...>
Date: 2008-02-23T01:22:05+09:00
Subject: Re: DateTime.new vs. DateTime.now

Thomas,

Thanks for that - that helps.

I guess I should have explained the reason I even bothered to look into 
this so deeply.

I really expected that DateTime.now would return the current, local 
time.  To me, this is against the grain of Ruby "doing what you would 
expect."

I needed to compare the current time with a time stored in local time. 
In order to do that, I have to capture DateTime.now, and then construct 
a new DateTime using DateTime.new with its components in order to get a 
local time that I can then use to calculate the difference between my 
stored time and the current time.

I've gotten past my problem, but it seems to me that DateTime.now should 
represent local time, and if I want gmt, then I can ask for something 
like DateTime.gmt.

If there is a simpler way to ask for a DateTime object that represents 
the current, local time, I was unable to find it.

Wes

-- 
Posted via http://www.ruby-forum.com/.