HP3000-L Archives

November 1999, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Tue, 30 Nov 1999 12:08:25 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Hi,

Barry Lake and Michael Hensley found what appears to be a new kind
of Y2K bug.  ("new" based on my searching the web for other reports.)

Basically, if you define a week as running from Sunday to Saturday,
the year 2000 has 54 weeks in it ... not the 52 or 53 code might expect.

This (54 weeks in a year) can happen only in a leap year, and only
in one leap year out of seven (i.e., in a leap year where January
1 is on a Saturday, which results in December 31 being a Sunday).

The last time this happened was 1972, well before most of our
date software was running!

Barry & Michael found some code in a customer's program that was
bounds checking user-entered "fiscal week" to be in the range
1..53.  In this particular case, 2000-12-31 was valid and would have
been fiscal week 54.

--
Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2