It looks like what we've done is turn the Y2K bug into a couple of dozen smaller bugs. I wonder if anyone is keeping track of the various dates the new bugs will pop up? >-----Original Message----- >From: Tony Forbes [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, January 11, 2000 6:03 PM >To: Mersenne@Base. Com >Subject: Re: Mersenne: The Second Mersennium Behind Us, How Now For >MyriadThe Third? > > >Aaron Blosser <[EMAIL PROTECTED]> writes >>Dunno 'bout all that, but another problem was that in order >to do a "quick >>and dirty" fix of the Y2K problem, a good number of people implemented >>windowing. Some used a window of 1930-2029 (which most >Microsoft software >>uses to interpret 2 digit years), some used 1940-2039, etc. >> >>That gives those idiots another 29 years to fix the software >the right way. > >One software company I know of is using a window of 1948-2047. So they >could have a date problem in 2048. Surely this is the real 'Y2K bug'. > >-- >Tony >_________________________________________________________________ >Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm >Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers > _________________________________________________________________ Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
