Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!XEROX.COM!AISupport.pasa
From: AISupport.pasa@XEROX.COM
Newsgroups: comp.sys.xerox
Subject: Re: End of DST
Message-ID: <871027-143250-1636@Xerox>
Date: Tue, 27-Oct-87 17:31:00 EST
Article-I.D.: Xerox.871027-143250-1636
Posted: Tue Oct 27 17:31:00 1987
Date-Received: Fri, 30-Oct-87 06:27:38 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 30

We have received the following information from development on the
workaround to the DST bug:


You may have noticed the time is a little bit off this week.  It turns
out that Lisp has an off-by-one bug that strikes in non-leap years in
which the month of the Daylight Savings Time change ends on a Saturday.
We're fixing Lisp, but that's not much help for today.  You can get your
clock back on track by pretending that October is a day shorter (for you
Lyric people, do this in an Interlisp exec):

(SETQ \EndDST 304)
(ADVISE '(\NS.SETTIME \PUP.SETTIME) 'AFTER '(SETQ \EndDST 304))

The ADVISE is necessary because the values Lisp gets from the time
server include the DST variable.  If you have a clock displayed on your
screen, you may have to kick the clock process--bring up a PSW from the
background menu, select the clock process, and click RESTART.

This problem will go away on Nov 1, at which time the advice will no
longer be necessary.

I believe the only negative side-effect of the advice is that you will
get the wrong DST indication if you inquire about dates in leap years in
which October ends on a Sunday (but then, you already get the wrong
answer for many years in the past in which DST did not occur, or
occurred at different times of year, since Lisp treats all years like
the present).

(courtesy of Bill vanMelle)