PHP 4.0 Bug #7103 Updated: 2037 latest year???

From: Date: Mon, 09 Oct 2000 21:28:16 +0000
Subject: PHP 4.0 Bug #7103 Updated: 2037 latest year???
Groups: php.dev 
Request: Send a blank email to php-dev+get-34528@lists.php.net to get a copy of this message
ID: 7103 Updated by: eschmid Reported By: michael@listevent.com Status: Closed Bug Type: Date/time related Assigned To: Comments: It's a limitation in the integers counting seconds from the first January since 1970. You need a 64 bit machine. Previous Comments: --------------------------------------------------------------------------- [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@listevent.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 --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=7103

« previous php.dev (#34528) next »