It's time for 64-bit time

[wilbert]

The main problem is how to ensure compatibility with old programs?
All date functions use the number of seconds since 1970/01/01
So how to set an earlier date and stay compatible?
Use negative values?
Change the initial date? (so it would take another library for the old programs to still work)

Indeed negative values for a date before 1970/01/01. That's the common approach.
And if that's not an option, a second more advance date library is also a possibility.
The same has been done with the VectorDrawing library.

If it was simple Fred would have done it a long time ago.

There have been multiple feature requests in the past that are not difficult to implement but haven't been implemented.
I think it's just a matter of choice.

[Fig]

+1
Fred could keep old 32 functions and add 64 ones...

[Kukulkan]

+1

[walbus]

I never really assumed that the old function should be rebuilt, but that a Time64 should be added....

[marcoagpinto]

+1

[Lord]

I also would appreciate an extended time function in PB.
But I think it will be not that easy to implement for dates
before 1970.
Look here:
http://www.purebasic.fr/english/viewtop ... 31&start=5
or here:
http://www.purebasic.fr/english/viewtop ... 37&start=9

[wilbert]

I also would appreciate an extended time function in PB.
But I think it will be not that easy to implement for dates
before 1970.

When you support dates from January 1, 1601 into the future, there are very little problems.
You just have to make clear it uses the Gregorian date system.
It's true of course that there are a lot of countries that don't use Gregorian dates or started using them after 1601 but in general I think it solves more problems than it creates.
At the moment it isn't even possible to represent a birthday from someone born before 1970.

[BarryG]

+1