From: Ross Bamford <rossrt@...>
Date: 2006-04-29T18:09:29+09:00
Subject: Re: time.parse fails for year values > 2037 (time out of range) in	ruby 1.8.4

On Sat, 2006-04-29 at 17:25 +0900, Peter Krantz wrote:
> I specifically need both date and time. I find it strange that a
> modern language like Ruby has this limitation. Looking at the
> documentation I find no mention of this.
> 
> To mee, this is a dangerous bug. People developing applications may
> not have thought about testing dates well into the future. The Time
> module needs an update to cope with a wider range of data. C# for
> example, handles values ranging from 12:00:00 midnight, January 1,
> 0001 Anno Domini (Common Era) to 11:59:59 P.M., December 31, 9999 A.D.
> (C.E.).

This isn't new, and it's not really a ruby problem:

	http://en.wikipedia.org/wiki/Year_2038_problem

Depending on what you're doing, couldn't you maybe use two Times, one as
a later base than 1970, and the other as an offset ?

-- 
Ross Bamford - rosco@roscopeco.REMOVE.co.uk