From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a0fe76afdfe9e57d
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-11 13:29:51 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsgate.duke.edu!newsfeed!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc04.POSTED!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: Re: milliseconds and delay until
References: <x7vu1aw4co2.fsf@pushface.org>
X-Newsreader: Tom's custom newsreader
Message-ID: <2jMFa.1200792$F1.141755@sccrnsc04>
NNTP-Posting-Host: 12.234.13.56
X-Complaints-To: abuse@attbi.com
X-Trace: sccrnsc04 1055363390 12.234.13.56 (Wed, 11 Jun 2003 20:29:50 GMT)
NNTP-Posting-Date: Wed, 11 Jun 2003 20:29:50 GMT
Organization: AT&T Broadband
Date: Wed, 11 Jun 2003 20:29:50 GMT
Xref: archiver1.google.com comp.lang.ada:39008
Date: 2003-06-11T20:29:50+00:00
List-Id: <comp.lang.ada>

> NB!! on most desktop machines you'll get a minimum actual delay of 10
> ms (a tick) or even 2 ticks; what happens, I think, is that many of
> the "delay until"s turn out to be delaying until a time that has
  See
http://www.adapower.com/reuse/tt.html
for a benchmarking program that will tell you how often your clock ticks,
minimum nonzero delay, etc.