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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,d1f23f0bd3971bec
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!news2.google.com!proxad.net!proxad.net!newsfeed.arcor.de!news.arcor.de!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Timing Block of GNAT code in milliseconds
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.14.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: <j44ad3vimbbd$.1ugquvdmos17o.dlg@40tude.net>
 <qLednUYN74JmCu_fRVn-iA@comcast.com>
Date: Sat, 30 Apr 2005 11:47:54 +0200
Message-ID: <9483czsw2g3h.1rxbqjt63e13m$.dlg@40tude.net>
NNTP-Posting-Date: 30 Apr 2005 11:47:49 MEST
NNTP-Posting-Host: e537932d.newsread4.arcor-online.net
X-Trace: 
 DXC==T]jETOO5XMZYo_CH;Uk?N:ejgIfPPldDjW\KbG]kaMHliQbn6H@_EI@ToZ317LmfB[6LHn;2LCVNCOgUkn_?_YOWiRECcWkSVG
X-Complaints-To: abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:10850
Date: 2005-04-30T11:47:49+02:00
List-Id: <comp.lang.ada>

On Fri, 29 Apr 2005 15:24:27 -0500, tmoran@acm.org wrote:

>> 2. Real_Time.Clock time is valid no longer next system boot.
> Why?  You could surely have a single black box located, say, in Greenwich
> England, which could be queried for time over the internet.

So it will be until next black box boot. (:-))

> Then you make
> a body for Real_Time.Clock that does that query to provide a time.  All of
> your programs on all of your distributed programs use the same library so
> they query the same box and get the same time.  The duration of a call to
> such a Real_Time.Clock might be long and might be variable, but that's
> true to some extent just running on a single multi-tasking machine.  If
> you want something faster and less variable, have each machine read from a
> time continually transmitted over a fiber optic cable from a central
> source.  There's no requirement that Ada.Real_Time use whatever low
> quality clock is provided by the particular computer it's running on.
> That just happens to be simpler, and adequate for most uses.

There are enough time service departments all over the world to create a
new one (per each application.) Why not to follow international standards?

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de