#7103 [Com]: 2037 latest year???
| From: | x dot x at x dot de | Date: | Fri, 04 Jun 2004 20:03:19 +0000 |
| Subject: | #7103 [Com]: 2037 latest year??? | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-60381@lists.php.net to get a copy of this message | ||
ID: 7103
Comment by: x dot x at x dot de
Reported By: michael at listevent dot com
Status: Closed
Bug Type: Date/time related
Operating System: Linux
PHP Version: 4.0.3RC2
New Comment:
The last date/time that is working:
19.01.2038 03:14:07 ( =2147480047 )
Previous Comments:
------------------------------------------------------------------------
[2000-10-09 17:28:16] 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:22:20] 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:21:06] 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:15:45] 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
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=7103&edit=1