The Y10K bug ???
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
Maciej Pirog wrote: Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! You know, you have a very valid point there, and an interesting one at that. Argh - my brain hurts. :rolleyes: ____________________ David Wulff Neil says: The following message could not be delivered to all recipients: dave i am a homosexual and i am in love with your father
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
Maciej Pirog wrote: Maybe your software will still be used! Even if it is, I won't be around so I don't really give a damn. Let the future generations go through the same crap we had to in 1999. :-D Michael :-) "Eureka" is Greek for "This bath is too hot"
-
Maciej Pirog wrote: Maybe your software will still be used! Even if it is, I won't be around so I don't really give a damn. Let the future generations go through the same crap we had to in 1999. :-D Michael :-) "Eureka" is Greek for "This bath is too hot"
Michael P Butler wrote: Let the future generations go through the same crap we had to in 1999. Yeah! Wasn't that fun?:mad: Let's Put The Fun Back In Dysfunctional! - My Darts Team T-shirt
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
Not a problem. By year 10000, all of Earth will have switched to hex notation for representing years. The real problem will be all those programs that only accept digits.
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
in that case, we may as well prepare for the year 100,000, or the year 1,000,000(:wtf:) i could go on, but cant be bothered, you get the picture.
:bob: Email: theeclypse@hotmail.com URL: http://www.onyeyiri.co.uk :bob:
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
I think the 64kbit architectures in use in the year 10,000 will make this a moot point. Of course, they'll still need to worry about the Y1MMMM bug, which will come to be known as the "M and M and M and M" bug. :) /ravi Let's put "civil" back into "civilization" http://www.ravib.com ravib@ravib.com
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
Well someone had better tell Microsoft. If they start now, then with luck they will have a bug free patch ready for COleDateTime by then :-D JohnJ http://www.rainbow-innov.co.uk
-
Michael P Butler wrote: Let the future generations go through the same crap we had to in 1999. Yeah! Wasn't that fun?:mad: Let's Put The Fun Back In Dysfunctional! - My Darts Team T-shirt
-
Roger Wright wrote: Yeah! Wasn't that fun? I thought it was a bit of overreaction really. Venet. -------- Black holes are where God divided by zero.(Steven Wright)
In retrospect, it may look that way. But there were some very good reasons to be concerned, and the hard work done by tens of thousands of technical experts before the event undoubtably prevented a great many serious failures. Even in the hardware store where I worked at the time, if I hadn't updated a number of systems before the event, we could well have been out of business in a couple of weeks. All our Point-of-Sale, online ordering, and office management systems would have ceased functioning correctly. The G/L, A/P, and A/R balances would have all gone out of whack, customer orders and deliveries would not have been completed, taxes would not have been paid on time, etc. Disaster for a small business, and the analyses and remediations I did, along with those from our suppliers, made 1/1/2000 just another day in the life:-) Let's Put The Fun Back In Dysfunctional! - My Darts Team T-shirt
-
I've Got an idea! Let's create date-storing classes based on STL or .NET collections! MP Maciej Pirog
YES....POWER to the dates!:laugh:
:bob: Email: theeclypse@hotmail.com URL: http://www.onyeyiri.co.uk :bob:
-
Not a problem. By year 10000, all of Earth will have switched to hex notation for representing years. The real problem will be all those programs that only accept digits.
:confused: Why hex? Did I miss something? What's preferable about it? I always thought the decimal system had some rather nice advantages (in a subconscious, unexplainable way, you know).
-Domenic Denicola- [CPUA 0x1337] MadHamster Creations "I was born human. But this was an accident of fate - a condition merely of time and place. I believe it's something we have the power to change..."
-
in that case, we may as well prepare for the year 100,000, or the year 1,000,000(:wtf:) i could go on, but cant be bothered, you get the picture.
:bob: Email: theeclypse@hotmail.com URL: http://www.onyeyiri.co.uk :bob:
I've Got an idea! Let's create date-storing classes based on STL or .NET collections! MP Maciej Pirog
-
Not a problem. By year 10000, all of Earth will have switched to hex notation for representing years. The real problem will be all those programs that only accept digits.
That will probably have taken care of itself over time, as we gradually evolve into a sixteen digit form. Of course, the presence of the NumPad on the right may skew evolution such that we might not have a symmetrical distribution of 8 digits on each hand. Let's Put The Fun Back In Dysfunctional! - My Darts Team T-shirt
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
Maciej Pirog wrote: Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! Hmm, my first reaction is, i'll be dead, so why care? But, on further consideration, what if there is developed a way to slow the aging process, so that i might live that long. And in the meanwhile, the job market changes, and all the cool, fun jobs (writing software for optical stereo systems in hot new languages like ZZ*=@#*! that replicate the elusive distortion introduced by the by-then archaic 128kbps MP3 encoding) are going to younger people. So the only thing that'll keep me employed is command of an archaic language that no-one wants to bother learning anymore, but has huge libraries of software needing maintenance. So, here's my plan: I'll write huge gobs of C++ and C# code, all with 4 character dates, being careful to ensure that the systems fail in extremely painful ways should a 5 character date ever occur. Then, i'll sit back and wait for job security. :D (BTW: Thanks for the heads-up on this; i might otherwise have shot my future career in the foot by using 64bit linear dates, etc.) --------
Laugh at your problems; everybody else does.
--Shog9 --
-
In retrospect, it may look that way. But there were some very good reasons to be concerned, and the hard work done by tens of thousands of technical experts before the event undoubtably prevented a great many serious failures. Even in the hardware store where I worked at the time, if I hadn't updated a number of systems before the event, we could well have been out of business in a couple of weeks. All our Point-of-Sale, online ordering, and office management systems would have ceased functioning correctly. The G/L, A/P, and A/R balances would have all gone out of whack, customer orders and deliveries would not have been completed, taxes would not have been paid on time, etc. Disaster for a small business, and the analyses and remediations I did, along with those from our suppliers, made 1/1/2000 just another day in the life:-) Let's Put The Fun Back In Dysfunctional! - My Darts Team T-shirt
Roger Wright wrote: Disaster for a small business, and the analyses and remediations I did, along with those from our suppliers, made 1/1/2000 just another day in the life lol. I cannot remember wery well, but was there an examlpe showing that Win2k bug is seriously damaging ? Or was it just the theory behind it? Venet. -------- Black holes are where God divided by zero.(Steven Wright)
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
Yeah, it#s a bit early, we should wait until ofter the world cup, when we can all concetrate on this tricky problem. Dude. Maybe we should switch all input to a base-36 system.
Back in the days before yer Gighertz and Teraflops there was something we old timers called paranoia. Andrew Torrance, The Lounge [sighist]
-
Roger Wright wrote: Disaster for a small business, and the analyses and remediations I did, along with those from our suppliers, made 1/1/2000 just another day in the life lol. I cannot remember wery well, but was there an examlpe showing that Win2k bug is seriously damaging ? Or was it just the theory behind it? Venet. -------- Black holes are where God divided by zero.(Steven Wright)
Sure. All sales on an accumulating G/L system suddenly rung up as 1978, instead of 2000. Safety systems - elevators, for example - which prevent operation unless reset periodically, and which rely on a date, rather than an interval (several models do). Most PCs we had in the company were ok, but a couple would have entered the wrong year in transactions, and a couple is much worse than all for the purposes of isolating a bad transaction. Our alarm system used a keep-alive timer that send a code based on the last reported date/time. It suddenly would have reported the last check as twenty years overdue, triggering an immediate alarm. Some of the local gas stations using older digital technology would have been unable to pump gas, putting emrgency personnel (and our own delivery trucks) out of service. If we'd had a night shift, the payroll would have given them 20 years of overtime. Our main office software (Mostly MS) was all non-compliant. All of these were smoothly upgraded prior to the event, and no glitches were suffered as a result. The only reason that we technocrats are not being regarded as heros is that we all did our jobs superbly, and transparently to the public. Our thanks was a few years of massive cutbacks in IT budgets and wave after wave of layoffs. Let the Luddites handle the next crisis; I'm sitting it out in my bombshelter surrounded by food, guns, and gold. Let's Put The Fun Back In Dysfunctional! - My Darts Team T-shirt
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
-
Hey developers! Maybe you think, that it's a bit too early, but that's what programmers in 1970s and 1980s were thinking! Computers had problems with year 2000, because they thaught that it was year 1900. Now think about year 10000. It will be a problem for computers! It's five chars (one more than now)! We have to redevelop our applications, redesign dialogs and reprogram our date-storing classes (like MFC CTime !!!). Too early? We have 8000 years? Don't be so sure. Maybe your software will still be used! The matrix has you! :suss: MP Maciej Pirog
time_t, as defined in most (if not all) UNIXes, is 32bit long, which means it'll wrap around in 2038. Many of us will be alive by then (though hopefully most will be retired.) Joaquín M López Muñoz Telefónica, Investigación y Desarrollo