New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timegm should be called with 4-digit year #16431
Comments
From perlbugbmw@lsmod.deCreated by perlbugbmw@lsmod.detimegm should be called with 4-digit year note: while this is only documentation, I found that some people do RTFM please review/test/merge this fix: --- perl-5.26.1.orig/pod/perlport.pod Perl Info
|
From @jkeenanOn Thu, 22 Feb 2018 10:17:25 GMT, perlbugbmw@lsmod.de wrote:
Pinging Dave Rolsky, upstream maintainer for Time::Local: Dave, okay to make this change in 'perlport'? Thank you very much. -- |
The RT System itself - Status changed from 'new' to 'open' |
From bitcardbmw@lsmod.deOn Thu, 22 Feb 2018 06:58:35 -0800, jkeenan wrote:
The Time::Local docs said, it should be this way, because 2-digit dates reference the rolling "current century" |
This is still broken in blead:
We do not want rolling century in that case. The epoch is always 1970, and not 2070, just because it is 2020 now. |
and not meant to be interpreted as 2070 because of rolling century. Fixes Perl#16431
and not meant to be interpreted as 2070 because of rolling century. Fixes Perl#16431
This should be changed, see http://blogs.perl.org/users/grinnz/2019/07/the-timelocal-trap.html for more info |
@autarch Can you comment on this proposed change to Thank you very much. |
+1 on this change. |
Thanks for the review. Pushed to blead in commit 57d341f. Closing ticket. Thank you very much. |
Migrated from rt.perl.org#132897 (status was 'open')
Searchable as RT132897$
The text was updated successfully, but these errors were encountered: