why does someone always have to bring up the "B" word
on a remarkable interesting post. :/
why does someone always have to bring up the "B" word
on a remarkable interesting post. :/
33... 23... who cares? (it was close to the end of the day and I was slowing down a tadOriginally Posted by LuckY
)
EntropySink. You know you have to click it.
Well it's something I'd never heard of before. Whether it'll have any significant impact in the future remains to be seen (although I think the chance of running 32bit machines in 33 years isn't as improbable as some people think - anyone remember the death of COBOL? No? That's because it's still out there). An interesting post nevertheless, so thanks to the OP.
You've NEVER heard of this???? Have you been in a cave?
EntropySink. You know you have to click it.
And offcoures using 64 bit microprocessorwill end up the problem.
But
using 64 bit microprocessor will be a escape from the problem means it is like hiding from problem by gettin back of 64 bit microprocessors.(Is that the way experts solves the problem?)
And for "33 years blah blah.." I would like to say that we all are still using C that developed in near 1970 and we are still using it and even posting our posts in one of message boards related to it.It is now 35 year old.does we stop using it?
Is it antique language?
By the way does any one belive in time travelers?
(Just being curious and fasinated)
Last edited by year2038bug; 08-30-2005 at 12:24 PM.
Anything that this could impact will likely be re-written by then or have 64 bit CPUs in them.
I doubt this will bother anything.
To code is divine
You seem surprised at this revelation. You should know that computers are lies upon lies. Yes, the problem will get pushed back, but you know by how much? If anybody has the maths to do it, please, I'm not sure how to calculate it, but my understanding is that it gets pushed back so much, it's not really going to matter.
It's not just 64bit processors. The important thing is a 64bit variable that holds the time. It's most likely possible to use a 64bit counter on 32bit systems. It's just a bit more expensive, but it beats the alternative.
It's relatively easy to go forwards in time (at an accelerated rate, I mean). Just get your spaceship close enough to a black hole that it's gravity will make you go really slow (in time). When you're ready, just get out of the gravity field. Congratulations, you've just gone forwards in time.
The problem is getting such a spaceship.
Either that, or get really drunk.
That I know of, going backwards in time is impossible.
SoKrA-BTS "Judge not the program I made, but the one I've yet to code"
I say what I say, I mean what I mean.
IDE: emacs + make + gcc and proud of it.
well, aside from your broken english, yes. that's generally how things work. when you have technology that no longer works, you create and implement new tech. isn't it so sad that at one time humanity only had an abacus to work with? imagine trying to get somebody to the moon with that
Join is in our Unofficial Cprog IRC channel
Server: irc.phoenixradio.org
Channel: #Tech
Team Cprog Folding@Home: Team #43476
Download it Here
Detailed Stats Here
More Detailed Stats
52 Members so far, are YOU a member?
Current team score: 1223226 (ranked 374 of 45152)
The CBoard team is doing better than 99.16% of the other teams
Top 5 Members: Xterria(518175), pianorain(118517), Bennet(64957), JaWiB(55610), alphaoide(44374)
Last Updated on: Wed, 30 Aug, 2006 @ 2:30 PM EDT
Pretty simple:
60 secs = 1 min
60 mins = 1 hour
24 hour = 1 day
365.25 = 1 year (approx)
Thus there are 31557600 sec / year
2^64 = 1.84467440737e19 (TI 86 calculation)
2^64 / 31557660 = 584,542,046,091 years
So pretty much our star will collapse and earth will cease to exist before that happens
Maybe I'm doing something wrong here, but:
2^32 / 31557600 = 136
Since UNIX time begain in 1970, shouldn't this bug occur in (1970 + 136) = 2106?
Last edited by Snip; 08-31-2005 at 08:36 AM.
Superman did it!
-Govtcheez
[email protected]
Technically, he didn't. He made Earth (and the people in it) do it, but it's good enough, I suppose.
@Snip:
I knew it was a bit more complicated than what Thantos wrote, you've just reminded me.
The singed bit, of course! The max value a 32 bit int can hold is actually 2^31, which gives you the right answer.
So in this line,
2^63 = 9223372036854777778
9223372036854777778 / 31557600 = 292271023045,31326140137399548762
Which is close enough to 292,271,023,045 giving us almost 300 billion (milliards for europeans) years to solve the problem (basically to move to 128 bit processors). I consider this enough, but you are free to disagree.
And if the numbers are short, in my defense I have to say that I'm runing a 32bit OS (although on a 64bit processor. I'll have to get my hands on a x64 Windows or get a wireless card that's supported (properly) undel Linux).
SoKrA-BTS "Judge not the program I made, but the one I've yet to code"
I say what I say, I mean what I mean.
IDE: emacs + make + gcc and proud of it.
According to Wikipedia, it is 2^31, not 2^32.
To code is divine
I'm of the belief that he actually flew around the whole universe, but the movie only showed him flying around earth because people wouldn't be able to comprehend him flying around the whole of existence.
I mean, c'mon - he's Superman!
-Govtcheez
[email protected]
I'm no expert, so whatever you say. The question is: Did he also go back in time?
SoKrA-BTS "Judge not the program I made, but the one I've yet to code"
I say what I say, I mean what I mean.
IDE: emacs + make + gcc and proud of it.
