Content deleted Content added
NawlinWiki (talk | contribs) icon |
m →The programming problem: corrected punctuation |
||
Line 35:
* In the [[Windows 3.1]] file manager, dates were shown as 1/1/19:0 for 1/1/2000. An update was available.
Even before [[January 1]], [[2000]] arrived, there were also some worries about [[September 9]], [[1999]] (albeit lesser compared to those generated by Y2K). This date could also be written in the numeric format, 9/9/99. This date value was frequently used to specify an unknown date; it was thus possible that programs might act on the records containing unknown dates on that day.<ref>[http://www.merlyn.demon.co.uk/critdate.htm Merlyn - Critical and Significant Dates - J R Stockton<!-- Bot generated title -->]</ref> It is also somewhat similar to the end-of-file code, 9999, in old programming languages. It was feared that some programs might unexpectedly terminate on that date. The bug, however, was more likely to confuse computer operators than machines.
Another related problem for calculations involving the year 2000 was that it was a [[leap year]] even though years ending in "00" are normally not leap years. A year is a leap year if it is divisible by 4 but not divisible by 100 unless also divisible by 400. For example, 1600 was a leap year, but 1700, 1800 and 1900 were not. Fortunately most programs were fixed in time, although the vast majority relied on the oversimplified rule that ''a year divisible by 4 is a leap year'', which works on 2000.
| |||