¢ Y2K bug fixing and testing should include the leap day period around February 29, 2000. Many test plans focus on the rollover from December 31, 1999 m January 1, 2000, where the largest number of bugs will be concentrated. Expanding tests to include Monday, February 28 2000 to Wednesday March 1 2000, or even to Sunday March 5 2000, can be a hard sdl. In this article I want to persuade you that the leap day period i is a time of serious risk to computer systems, and to discuss algorithms for dealing correctly with dates over a time span of more than 4000 years. Although correct implementation of date ii~ ~ conversion routines is essential to avoiding the leap day year 2000 bug, there is another reason for looking into the code: it ' will lead us into some thoughts on generality, clarity, and efficiency in APL coding styles which may be of use to the educational community, Illmt~6on ~ b y Jon N c G r e w . P h o t o o f have seriousJan. 1 2000 problems m fix?" This is not a rhetori- ~ cal quesfion--I have heard it expressed
/lp/association-for-computing-machinery/pope-gregory-on-mars-on-february-31-2000-NpigZOYF3g