Re: Timing Block of GNAT code in milliseconds

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

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