php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #7103 2037 latest year???
Submitted: 2000-10-09 17:15 UTC Modified: 2000-10-09 17:28 UTC
From: michael at listevent dot com Assigned:
Status: Closed Package: Date/time related
PHP Version: 4.0.3RC2 OS: Linux
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: michael at listevent dot com
New email:
PHP Version: OS:

 

 [2000-10-09 17:15 UTC] michael at listevent dot com
When creating a calendar application ... everything works fine until year 2038. Then it breaks. Is there any reason for limiting the date/time functions to 2037 years?

http://durras.listevent.com/year.php?year=2037
http://durras.listevent.com/month.php?year=2037&month=12

Thanks,

Michael

Patches

yearlimit (last revision 2013-08-26 08:02 UTC by udom at sut dot ac dot th)

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-10-09 17:21 UTC] derick@php.net
In 2038 Unixes have their "millennium bug". The 32 bits second counter (seconds sinds 1970) is out of bits then.
It should be fixed, but not very important at the moment (I think).
 [2000-10-09 17:22 UTC] eschmid@php.net
It's a limitation in the integers counting seconds from
the first January since 1970. You need a 64 bit machine.
 [2000-10-09 17:28 UTC] eschmid@php.net
It's a limitation in the integers counting seconds from
the first January since 1970. You need a 64 bit machine.
 [2004-06-04 22:03 UTC] x dot x at x dot de
The last date/time that is working:

19.01.2038 03:14:07 ( =2147480047 )
 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Sat Jan 29 08:03:34 2022 UTC