You say you don't have enough to worry about with the Y2K scare? Well, that's what the Leap Year Glitch is for, friends - some computer programmers and Y2K officials are pondering the potential for a leap year kink to ruin March 2000.
You see, Feb. 29 is the first "leap day" in a turn-of-the-century year since 1600, according to Wired, and Y2K czar John Koskinen has told ABC's This Week that there's a potential for computer-related problems on that day, too, thanks to a calendar oversight.
Thing is, he tells This Week, the first year of a new century isn't a leap year "unless it's divisible by 400. And it turns out enough people didn't understand that, that they programmed year 2000 as a non-leap year" when it really is one.
Koskinen told the program his team would take similar precautions to those for Y2k, though not quite so extensive. "We will monitor whatever happens on (Feb.) 29" - just as they plan to do for Jan. 1. Meanwhile, a spokesman for the President's Council on the Year 2000 tells the Washington Times the leap year glitch doesn't really offer a threat - because most computers testing for the Y2K bug also tested for leap year.
