Brian said:
Indeed, I always wondered why people insisted on calling the centuary
bug 'the millenium bug' or the 'Y2K bug'.
But it's really more often than that. There are all sort of ways that
various software encodes dates internally. Each of these can introduce
its own problems.
There was one on 9th September 2001. (10**9 seconds since 1970).
Of course there's the famous 'Unix' one on 19th January 2038 (2**31
seconds since 1970).
There's a lesser known one one a couple of years earlier (2**32 seconds
since 1900).
There's even one in 2010 that some users of systems written in the MUMPS
programing language may hit.
IBM mainframes started to have "keep forever" files deleted on August
16th, 1972, which was 9999 days before 2000-01-01.
(There was also a beta version of OS/VS1 that crashed every 24 hours at
exactly midnight, GMT, with a zero-divide error in the nucleus, because
one of the programmers who wrote the date/time code was aware that 1900
was not a leap year, and another one wasn't.)
--
John W. Kennedy
"The pathetic hope that the White House will turn a Caligula into a
Marcus Aurelius is as naïve as the fear that ultimate power inevitably
corrupts."
-- James D. Barber (1930-2004)