Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site hadron.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.lang.c
Subject: Re: Daylight Savings Time
Message-ID: <126@hadron.UUCP>
Date: Wed, 18-Dec-85 01:42:20 EST
Article-I.D.: hadron.126
Posted: Wed Dec 18 01:42:20 1985
Date-Received: Fri, 20-Dec-85 02:14:10 EST
References: <124@brl-tgr.ARPA> <1727@uw-beaver> <1679@hammer.UUCP> <641@mit-eddie.UUCP>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 23

In article <641@mit-eddie.UUCP> barmar@mit-eddie.UUCP (Barry Margolin) writes:
>On Multics, the date/time conversion software includes a table listing
>many of the world's time zone names (in several languages, no less),
>along with the corresponding difference from GMT.  ...

Nice, but nothing special and not unique to Multics.  I had this
working on an old PWB 1.0 system quite a few years ago.

>                             -- the system administrators merely change
>the default time zone twice a year (if necessary -- our primary exposure
>system is in Arizona, which doesn't use DST).  Many of our customers are
>outside the US, so hardcoding our DST rules would have been a nightmare.

Many systems don't have system administrators (at least not ones who
are like you and me and know how to wreak magic), and so it is nice
if they automagically put in the correct times.  If there is a
computable algorithm, it can be expressed on the computer in some
simple form, even if only via numerical methods.

joe
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}