Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!CS.ROCHESTER.EDU!koomen
From: koomen@CS.ROCHESTER.EDU
Newsgroups: comp.sys.xerox
Subject: Re: End of DST
Message-ID: <8710261945.AA12911@cursa.cs.rochester.edu>
Date: Mon, 26-Oct-87 16:22:31 EST
Article-I.D.: cursa.8710261945.AA12911
Posted: Mon Oct 26 16:22:31 1987
Date-Received: Wed, 28-Oct-87 19:40:37 EST
References: <12345600160.25.LANE@SUMEX-AIM.STANFORD.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 19

Christopher, 

thanks for digging further.
If it is true that Lisp "calls \CHECKDSTCHANGE with YDAY based on
January 1 = 0" then instead of changing the math (GREATERP -> GEQ) it
would perhaps be more appropriate for \NS.SETTIME to set \EndDST to
SUB1 of whatever the network returns.  And, indeed, changing \EndDST
305->304 instead of 305->298 does the trick as well.

Curiously, as far as I can tell the above assumption is incorrect.
Today, Oct 26, is the 299th day of the year, and tracing \CHECKDSTCHANGE
shows it is called with 299, not 298.

So perhaps the problem lies in the interpretation of \EndDST.  We might
be dealing with a boundary case, in that this year the 305'th day is a Sunday.
Does DST end on the [last Sunday <= \EndDST] or [last Sunday < \EndDST]?
Curently the algorithm uses the former which gives the incorrect result.

-- Hans