Date - Problem with year 2038

[Josemar]

Hi all

Please, is it a estimation of solving this problem in PureBasic?

https://www.purebasic.com/documentation/date/index.html

Regards

[Rinzwind]

Somewhere around 2039

[BarryG]

This has been brought up over and over and over but it's never been fixed.

People have posted their own solutions - I use the Date64 module here -> https://www.purebasic.fr/english/viewto ... 07#p478507

BTW, my Samsung Galaxy S9 phone (running Android 10) only lets me set the date up to 31 Dec 2037, which shocked me.

[chi]

Somewhere around 2039

Sad but true

[benubi]

This is because Unix dates are only 32bit. There will certainly exist a 64bit version one day. In fact 64bit OS's already use them internally. Basically the problem should evaporate when there won't be any 32bit computers and OS's in broad usage. The zip archives and file systems etc. will have to support 64bit dates instead of what they are using now. According to wikipedia a few OS's have already solved the problem (internally) by using 64bits in their new OS versions (32bit and 64bit versions). Now the problem is what you want that 64bit value to be for interoperability/new standards, some people would like to have the time in microseconds, have leap seconds and other features implemented, so there is in fact no real solution that would satisfy everybody.

https://en.wikipedia.org/wiki/Year_2038 ... #Solutions

[mk-soft]

Even if the one from Wibert Date64 is the right one, I wrote a module that supports the API from the respective OS.
(Window, macOS (Intel/M1) and Linux (Intel/Arm)). So it runs also with C-backend like macOS M1 and Raspberry ARM.
For the CalendarGadget there are also functions to set and read the date.

Link: Module DateTime as Double since 1970