On Thu, 31 Dec 2020 19:03:41 GMT, Charlie Gibbs
Post by Charlie Gibbs Post by David LaRue
During High School we had access to an HP-2000/Access timeshare
system. I found that the system time wrapped oddly on New Year. It
rolled over to December 32 of the same year. The System Operator had
to manually update the date at the start of the new year.
Were there other systems that didn't handle December to January rollovers?
Hell, early versions of MS-DOS didn't even handle midnight rollover
reliably. A 10-line BASIC program that shows date and time whenever
either one changes would produce output with various combinations of
some, all, or none of the following, depending on version, machine,
Been there, done that, wrote nasty code to deal with it.
Fred Brooks, in _The Mythical Man-Month_, describes the decision to
omit code that handled February 29 in leap years, to save 100 bytes.
I tried searching for this and I got
according to Brooks, who had been one of the the projects managers in
the 1960s, a typical second system. And to support his claim that it was
overblown and wasteful, he offers this example:
For example, OS/360 devotes 26 bytes of the permanently resident date-
turnover routine to the proper handling of December 31 on leap years
(when it is Day 366). That might have been left to the operator.
Bah, and indeed, Humbug.