Year 2038 problem in GHC 6.4.2 runtime
As far as I can see, the current (6.4.2) GHC runtime suffers the year 2038 problem; that is, the System.Time module does not support dates from 2038 onwards (the code below reproduces the problem). Is this bug scheduled to be fixed in the near future (my search in Trac yielded nothing) ? Regards, Cyril ___ The following code reproduces the problem with the Windows distribution of GHC 6.4.2: module Main where import System.Time main = putStrLn $ show $ toClockTime $ CalendarTime 2038 January 31 12 0 0 0 Sunday 0 "GMT" 0 False
Hello Cyril, Friday, September 22, 2006, 6:16:44 PM, you wrote:
As far as I can see, the current (6.4.2) GHC runtime suffers the year 2038 problem; that is, the System.Time module does not support dates from 2038 onwards (the code below reproduces the problem).
there is new Time library, which is supposed to replace old System.Time. we hope that it will happen before 2038 :D -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com
Bulat, I am afraid I would need the new Time library a little earlier than 2038, because I am working on financial software where it is not uncommon to have contracts over 30 years long. Is the new Time library available for download? Regards, Cyril ___ Bulat Ziganshin wrote:
there is new Time library, which is supposed to replace old System.Time. we hope that it will happen before 2038 :D
Hello Cyril, Tuesday, September 26, 2006, 1:30:23 AM, you wrote:
I am afraid I would need the new Time library a little earlier than 2038, because I am working on financial software where it is not uncommon to have contracts over 30 years long.
of course i'm joking. i even don't known is this library solves this problem or not
Is the new Time library available for download?
http://semantic.org/TimeLib/ moreover, it will be bundled with ghc 6.6 -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com
Hello Bulat,
moreover, it will be bundled with ghc 6.6
That's much better news, thanks! Your previous posting sounded overly pessimistic (it even made it to the Quotes of the Week section of HWN) Cheers, Cyril
On Fri, Sep 22, 2006 at 04:16:44PM +0200, Cyril Schmidt wrote:
As far as I can see, the current (6.4.2) GHC runtime suffers the year 2038 problem; that is, the System.Time module does not support dates from 2038 onwards (the code below reproduces the problem).
We inherit the problem from C's mktime, which returns a time_t, so this is not trivial to fix. As Bulat says, I don't think the new time package will suffer from this problem. Thanks Ian
participants (3)
-
Bulat Ziganshin -
Cyril Schmidt -
Ian Lynagh