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'
1073741824 | decimal |
40000000 | hex |
10000000000 | octal |
1000000000000000000000000000000 | binary |
And just think, you were there.
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!)
Congratulations! You beat me to it by a day:
But at least I had the grace to attribute the source:
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...
Ooh, thanks for the reminder. I would've missed it otherwise.
did the world end?
Yes, but it was restored from backup.
oh that's why I'm hungry again!
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]
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?
But I had posted a countdown(well, up) clock I wrote in Javascript:
http://staticfree.info/blog/code/binaryCountdownClock.comments
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.
Damn, beat me to it!
h00z h0 'leet
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