Another possibility...
Port the Date object implementation from ECMA/Javascript.
It has a range of +/-8.64e15, or Tue, 20 Apr -271821 00:00:00 GMT to Sat, 13
Sep 275760 00:00:00 GMT.
You know...just to have a little extra time to find something else. ;)
- Jon L.
On Wed, May 7, 2008 at 12:56 AM,
Quoting Jon L. [EMAIL PROTECTED]:
Another possibility...
Port the Date object implementation from ECMA/Javascript.
It has a range of +/-8.64e15, or Tue, 20 Apr -271821 00:00:00 GMT to Sat, 13
Sep 275760 00:00:00 GMT.
You know...just to have a little extra time to find something else. ;)
- Jon
On Tue, May 6, 2008 at 11:56 PM, Paul Scott [EMAIL PROTECTED] wrote:
On Tue, 2008-05-06 at 23:50 -0600, Nathan Nobbe wrote:
true-that ;)
anyway, the DateTime class is implemented as a 64-bit unsigned (i think)
value. so if you use it you should be good to go.
php echo
On Wed, May 7, 2008 at 12:48 AM, Kalle Sommer Nielsen [EMAIL PROTECTED] wrote:
Quoting Jon L. [EMAIL PROTECTED]:
Another possibility...
Port the Date object implementation from ECMA/Javascript.
It has a range of +/-8.64e15, or Tue, 20 Apr -271821 00:00:00 GMT to Sat,
13
Sep 275760
On Wed, 2008-05-07 at 00:54 -0600, Nathan Nobbe wrote:
looks like mine only goes to dec. 31, =/
*Gasp!* best you get cracking on finding an alternative solution!
--Paul
All Email originating from UWC is covered by disclaimer
-Original Message-
From: Paul Scott [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 9:12 AM
To: Nathan Nobbe
Cc: Kalle Sommer Nielsen; Jon L.; Chetan Rane; php-general@lists.php.net
Subject: Re: [PHP] the Y2K38 BUG
On Wed, 2008-05-07 at 00:54 -0600, Nathan Nobbe wrote:
looks
On Wed, May 7, 2008 at 1:11 AM, Paul Scott [EMAIL PROTECTED] wrote:
On Wed, 2008-05-07 at 00:54 -0600, Nathan Nobbe wrote:
looks like mine only goes to dec. 31, =/
*Gasp!* best you get cracking on finding an alternative solution!
yes, me and the rest of the immortal gang are all
On Wed, May 7, 2008 at 11:34 AM, Nathan Nobbe [EMAIL PROTECTED] wrote:
On Wed, May 7, 2008 at 1:11 AM, Paul Scott [EMAIL PROTECTED] wrote:
On Wed, 2008-05-07 at 00:54 -0600, Nathan Nobbe wrote:
looks like mine only goes to dec. 31, =/
*Gasp!* best you get cracking on
Hi all
Have guys heard of the the Y2K38 Bug more details are on this link
http://www.codeproject.com/KB/bugs/The-Year-2038-Bug.aspx
Can there be a possible solution. As the system which I am developing for my
client uses Unix timestamp.
This might effect my application in the future
On Wed, 2008-05-07 at 10:03 +0530, Chetan Rane wrote:
Have guys heard of the the Y2K38 Bug more details are on this link
Nope, but I can guess what its about.
Can there be a possible solution. As the system which I am developing
for my client uses Unix timestamp.
There are probably
On Tue, May 6, 2008 at 10:57 PM, Paul Scott [EMAIL PROTECTED] wrote:
On Wed, 2008-05-07 at 10:03 +0530, Chetan Rane wrote:
Have guys heard of the the Y2K38 Bug more details are on this link
Nope, but I can guess what its about.
Can there be a possible solution. As the system which I am
Seriously If your apps are still being used in 2038 ... WOW!
This is an issue that will more then likely be well resolved LONG before
2038...
On 5/6/08 10:50 PM, Nathan Nobbe [EMAIL PROTECTED] wrote:
On Tue, May 6, 2008 at 10:57 PM, Paul Scott [EMAIL PROTECTED] wrote:
On Wed,
On Tue, 2008-05-06 at 23:50 -0600, Nathan Nobbe wrote:
true-that ;)
anyway, the DateTime class is implemented as a 64-bit unsigned (i think)
value. so if you use it you should be good to go.
php echo date_create('2040-10-24')-format('M-d-Y');
Oct-24-2040
a 64bit unsigned int is best,
13 matches
Mail list logo
