From: Christian Neukirchen Date: 2006-04-30T06:20:27+09:00 Subject: Re: time.parse fails for year values > 2037 (time out of range) in ruby 1.8.4 "Peter Krantz" writes: > On 4/29/06, Christian Neukirchen wrote: > >> This is not a limitation of Ruby, but of your operating system. If >> you have a OS which time_t is 64-bit (e.g. 64-bit AIX), you can use >> Time well beyond 2038. > > I don't agree. Other laguages typically implement this type of core > functionality independently of the OS. E.g. Python and C# both support > datetime constructs without this limitation on 32-bit systems. Making > the language dependent on OS libraries reduce portability. Citing http://ftp.python.org/doc/lib/module-time.html: > The functions in this module do not handle dates and times before > the epoch or far in the future. The cut-off point in the future is > determined by the C library; for Unix, it is typically in 2038. > ... > Python depends on the platform's C library Python however provides a native DateTime implementation since 2.3. >> If you need a bigger range, check for Date and DateTime; these >> libraries are a lot slower than native Time, however. > > DateTime has the same limit (I believe it uses the Time library as > well). Date does not support time. As mentioned, it does. > Peter Krantz -- Christian Neukirchen http://chneukirchen.org