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
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,763df80c3d6aae03
X-Google-Attributes: gid103376,public
From: "Robert I. Eachus" <eachus@mitre.org>
Subject: Re: Delay guarantees
Date: 1999/05/28
Message-ID: <374F2885.D47229FC@mitre.org>#1/1
X-Deja-AN: 483293380
Content-Transfer-Encoding: 7bit
References: <3749EE1A.94483DF@mitre.org> <374A093C.D352D3A1@home.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Organization: The MITRE Corporation
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-05-28T00:00:00+00:00
List-Id: <comp.lang.ada>

Bryce Bardin wrote:
 
> Case 3) is, of course, the effect of section 9.6(20) of the Ada
> Reference
> Manual, which says, in part:
> 
> For a delay_relative_statement, the expiration time is defined as
> the current time, in the time base associated with relative delays,
> plus the value of the delay_expression converted to the type
> Duration, and then _rounded up to the next clock tick_.

    If you are going that far, you really should quote the next
sentence:

    The time base associated with relative delays is as defined in D.9,
"Delay Accuracy" or is implementation defined.

    Translation:  If the compiler supports the real-time annex, you can
look it up.  Otherwise ask your vendor. ;-)

-- 

                                        Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...