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.3 required=5.0 tests=BAYES_00,INVALID_MSGID,
	MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ca9c3c589691f97e,start
X-Google-Attributes: gid103376,public
From: fmanning@my-dejanews.com
Subject: Delay guarantees
Date: 1999/05/20
Message-ID: <7i1m4b$cb1$1@nnrp1.deja.com>#1/1
X-Deja-AN: 480206285
X-Http-Proxy: 1.0 PROVIDER,
 1.0 x30.deja.com:80 (Squid/1.1.22) for client 208.235.167.9
Organization: Deja.com - Share what you know. Learn what you don't.
X-Article-Creation-Date: Thu May 20 19:00:29 1999 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows 98)
Date: 1999-05-20T00:00:00+00:00
List-Id: <comp.lang.ada>

If you have a delay relative statement, does the delay argument
guarantee a minimum delay? For example:

   Delay 0.5;

Does this guarantee a minimum 500 ms delay?

According to the Ada 95 style guide at adaic, "The Ada language
definition only guarantees that the delay time is a minimum." The guide
also warns against depending on achieving a particular delay, but to
the extent that a delay is achievable, the implication seems to be that
a minimum is guaranteed.

But in the LRM, in section D.9 on Delay Accuracy, the only applicable
requirement I can find is in paragraph 3. To paraphrase -- if you read
the clock before and after a delay statement, the time difference must
be equal or greater than the delay argument.

Suppose the delay argument is equivalent to a single clock tick, and
the delay is executed just before a tick? Can delay return just after
the tick? If so, the actual time delay could be essentially 0.

-- Frank Manning
-- NetMedia, Inc.


--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---