From: zzqzpfynevsei@... (xor) Date: 2004-04-11T07:54:16+09:00 Subject: Re: Time upper limit Gregory Millam wrote in message news:<20040410123059.5523c204@ozymandias.lethalcode.net>... > Received: Sun, 11 Apr 2004 00:49:16 +0900 > And lo, xor wrote: > > > What are the upper limit on the values for Time class and where are they documented? > > > > for: > > @someTime = Time.utc(2100) > > I am getting > > in `utc': time out of range (ArgumentError) > > > > On the other hand > > @someTime = Time.utc(2020) > > does not generate any errors. > > > > (New to Ruby) > > > This isn't a ruby thing, it's a system thing. > > Seconds count from January 1, 1970. And because of 32 bit limitations on most systems, that means a last possible date of January 18, 2038 Ahem.... why is it a system thing? I am new to Ruby, so I may be missing something. Other cross platform languages do not have this limitation, in Java, the following runs fine on WindowsXP: Data d = new Date(10000,1,1) Does this mean that Ruby programs running on a 64 bit OS may fail on a 32 bit OS? And how does one goes about representing the year 2050 in Ruby? Sorry about all those questions, last one, where is this behavior documented ?