Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!gate.ready.com!gate.ready.com!glenn
From: glenn@ready.com (Glenn Kasten)
Newsgroups: comp.lang.forth
Subject: Re: misc ?s on BASIS15
Message-ID: <1991May6.153631.4108@ready.eng.ready.com>
Date: 6 May 91 15:36:31 GMT
References: <587@rc6.urc.tue.nl>
Sender: glenn@ready.eng.ready.com (Glenn Kasten)
Reply-To: glenn@ready.com (Glenn Kasten)
Organization: Ready Systems
Lines: 24


In article <587@rc6.urc.tue.nl>, wsbusup4@rw5.urc.tue.nl (Jan Stout) writes:
|> 
|>  8.2.1645 GET-DATE
|> 
|>           Where is SET-DATE?
|> 	  Furthermore I think DATEs should only refer to day/month/year
|> 	  so I suppose GET-TIME (and SET-TIME) for the sec/min/hour would be
|> 	  better. At least it would reduce the ridiculous number of
|> 	  stackentries.
|> 

I agree that there should be a SET-DATE.  I disagree that GET-TIME should
be a separate word, as that would introduce a race condition when you need
to get both the date and time at midnight.  It is unclear from the
specification whether GET-DATE returns the local date and time, or
universal coordinated time.  I suggest that the interface be changed
to look more like POSIX.1's support for date and time - a lot of work
went into making that interface be (mostly) complete.

-- 
Glenn Kasten
Ready Systems 470 Potrero Ave. Sunnyvale CA 94086 
glenn@ready.com (408) 522-7357