Page 1 of 1

ParseDate limited to 2037

Posted: Sat Jul 15, 2017 10:41 pm
by IdeasVacuum
PB5.6 Win7x86
Hmm:
Success

Code: Select all

sCurrentDate.s = "19/04/2037"
Debug ParseDate("%dd/%mm/%yyyy",sCurrentDate)
Failure

Code: Select all

sCurrentDate.s = "19/04/2038"
Debug ParseDate("%dd/%mm/%yyyy",sCurrentDate)
Seems odd to me since 19/04/2038 is a valid date and it's not sooo far in the future......

Re: ParseDate limited to 2037

Posted: Sat Jul 15, 2017 10:50 pm
by Sicro
PureBasic - Date

Overview
[...]
Note: supported date/time values are 1970-01-01, 00:00:00 for the minimum and 2038-01-19, 03:14:07 for the maximum.
GPI and I have collected a few codes that support extended dates: DateX, DateAndTimeA, Date64
https://github.com/SicroAtGit/PureBasic ... aster/Date

Re: ParseDate limited to 2037

Posted: Sun Jul 16, 2017 12:36 am
by IdeasVacuum
That is a cool selection of time toys Sicro, thanks 8)

Re: ParseDate limited to 2037

Posted: Sun Jul 16, 2017 1:43 am
by Dude
Sicro wrote:GPI and I have collected a few codes that support extended dates
They're nice workarounds for now, but PureBasic really needs to support this natively.

Re: ParseDate limited to 2037

Posted: Sun Jul 16, 2017 10:44 am
by Sicro
Hello Dude

Missing features can be inserted with includes. So we can also take care of adding features and the PB developer does not have all the work.
At the native date library I give you but right. That should really be expanded by the PB developers.

Re: ParseDate limited to 2037

Posted: Mon Jul 17, 2017 6:41 am
by netmaestro

Re: ParseDate limited to 2037

Posted: Mon Jul 17, 2017 11:18 am
by IdeasVacuum
It is very interesting - especially the contribution from another frog!

Re: ParseDate limited to 2037

Posted: Sat Nov 04, 2017 12:28 pm
by CONVERT
Thanks to netmaestro and wilbert (http://www.purebasic.fr/english/viewtop ... 12&t=56031)

I agree: PureBasic really needs to support this natively.