Page 1 of 1
Support for 64-bit Date()
Posted: Sat Nov 13, 2010 7:43 am
by Mistrel
Date() is still using the old 32-bit POSIX time which will wrap around in 2038. Granted, that's still 27 years in the future, but it's still a problem that can affect calculations that deal with future time much earlier.
Re: Support for 64-bit Date()
Posted: Sat Nov 13, 2010 10:21 am
by KJ67
+1
I ran into this issue during the summer when I was doing a small app for the office, simply speaking so ended all younger colleges up with very odd amount of years left.
Re: Support for 64-bit Date()
Posted: Sat Nov 13, 2010 5:08 pm
by Demivec
I think this is useful also. The currently Date library is limited to roughly a 68 year range of time. I would be in favor of changes to support a 64-bit Date().
Re: Support for 64-bit Date()
Posted: Sat Nov 13, 2010 9:43 pm
by Seymour Clufley
What would be the date limits with 64-bit?
Re: Support for 64-bit Date()
Posted: Sun Nov 14, 2010 12:29 am
by Mistrel
Seymour Clufley wrote:What would be the date limits with 64-bit?
Approximately 292 billion years.
Re: Support for 64-bit Date()
Posted: Sun Nov 14, 2010 2:40 pm
by blueznl
I can live with that
Re: Support for 64-bit Date()
Posted: Sun Nov 14, 2010 7:33 pm
by Little John
This has been discussed repeatedly.
We can even now easily access a bigger range of dates than the current PB library does, see
http://www.purebasic.fr/english/viewtopic.php?t=33714
Regards, Little John
Re: Support for 64-bit Date()
Posted: Thu Dec 22, 2011 9:24 am
by MachineCode
+1
Re: Support for 64-bit Date()
Posted: Tue Jan 17, 2012 4:20 pm
by Hysteria
I'd really like to see this too. I've been writing a little app that needs to go much further back than 1970 and far prefer native solutions to workarounds.
While on the subject, it would be great to be able to use 'setgadgettext' with a date gadget given that 'getgadgettext' is capable of reading it. That would avoid the need to use date() at all in this instance.