| 1000000000000000000000000000000 seconds |
[Sat, 10-Jan-2004 5:21 AM] |
In sixteen minutes -- at Sat Jan 10 05:37:04 2004 PST, or Sat Jan 10 13:37:04 2004 GMT -- time_t will be a 31 bit quantity. That is, the number of seconds since the Unix Epoch (Thu Jan 1 00:00:00 1970 GMT) will be 2^30. | 1073741824 | decimal | | 40000000 | hex | | 10000000000 | octal | | 1000000000000000000000000000000 | binary | And just think, you were there. perl -e 'print localtime(2**30) . "\n"' perl -e 'printf "%b\n", time'
|
|
|
| Comments: |
Was it as good for you as it was for me?
Hah! LJ's timestamp certainly fucked that post up.
stop stealing from my picture set!
(well, it's not "my" picture set, but, ummm... i was here first!)
From: vincel Sun, 11-Jan-2004 12:06 PM (UTC)
| (Link)
|
Congratulations! You beat me to it by a day: bleach 20% ls -l 728127 -rw-r--r-- 1 vincel wheel 2912 Jun 28 2003 728127 bleach 21% ls -l 353803 -rw-r--r-- 1 vincel wheel 1682 Jun 27 2003 353803 But at least I had the grace to attribute the source: bleach 22% identify -verbose 728127 Image: 728127 ... comment: Copyright (c) 2003 by Peter Stemmler -- QuickHoney http://www.quickhoney.com/
I just attempted to explain this to my fianceé... She suddenly got serious and asked, "Is this like Y2K?"
That just made my morning.
No, that doesn't happen until 2038...
eric@haleakala [10:25am] ~ 3 $ perl -le 'print scalar localtime(2**31-1)'
Mon Jan 18 19:14:07 2038
eric@haleakala [10:25am] ~ 4 $ perl -le 'print scalar localtime(2**31)'
Fri Dec 13 12:45:52 1901
![[User Picture]](http://l-userpic.livejournal.com/81048954/111931) | From: avva Sat, 10-Jan-2004 5:47 AM (UTC)
| (Link)
|
Ooh, thanks for the reminder. I would've missed it otherwise.
![[User Picture]](http://l-userpic.livejournal.com/5887295/515656) | From: jwz Sat, 10-Jan-2004 6:21 AM (UTC)
| (Link)
|
Yes, but it was restored from backup.
oh that's why I'm hungry again!
![[User Picture]](http://l-userpic.livejournal.com/9646191/1270877) | From: cannery Sat, 10-Jan-2004 9:36 AM (UTC)
cat shit | (Link)
|
That explains the more than normal amount of cat shit in the trays tonight.
"My son returns from a fancy East coast college and I'm horrified to find he's a nerd"
[j]
![[User Picture]](http://l-userpic.livejournal.com/25365050/1026394) | From: insom Sat, 10-Jan-2004 6:49 AM (UTC)
| (Link)
|
It's not a comedy.
And I turn 31! tomorrow...
31! ?! Gotd dammit, you're old.
So, um, since you'd have been there - what colour were the dinosaurs?
![[User Picture]](http://l-userpic.livejournal.com/7404641/747451) | From: xxv Sat, 10-Jan-2004 8:53 AM (UTC)
It's a bit too late... | (Link)
|
hehe. i posted in my journal on this when slashdot ran a story. AFAIK it's really only a problem for applications that make use of 30b timestamps, which the best that I vould discern lisp would be the major thing affected there? I actually did the man on when the 'world will end'. It's fun to think we will encounter this same problem every so often, im not going to do the math, but when will a 64b timestamp be forced to rollover? I wonder if we will have a y2k repeat around then or not. (yes i realize the y2k problem wasnt a MAX_INT rollover)
I'm just thoroughly amused that the GMT time is 1337.
64bit WILL save the day!!!
As a side note, the "l" (el) switch in Perl will cause a newline to be added after each print. It makes one-liners easier (though the localtime will have to be forced into scalar context).
perl -le 'print scalar localtime(2**30)'
perl -le 'printf "%b", time'
and lets not forget it was also my friggin birthday. sigh though two hours off | |