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-Thread: 103376,d1f23f0bd3971bec X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail NNTP-Posting-Date: Fri, 29 Apr 2005 15:24:27 -0500 From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Timing Block of GNAT code in milliseconds References: X-Newsreader: Tom's custom newsreader Message-ID: Date: Fri, 29 Apr 2005 15:24:27 -0500 NNTP-Posting-Host: 24.6.127.15 X-Trace: sv3-vENhXCvdYiif8DTmi+b/ZnUtjxHKA946NZl4iPECe1bVAGAOfY1hp7CjrAxN8YIt215yvkD7ekdcQYR!jEauHQZgfwJWFx9w8oN/DcuKb7yg90VX1VZREHlOFWVN9jDuhR66lHoizbU= X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Xref: g2news1.google.com comp.lang.ada:10833 Date: 2005-04-29T15:24:27-05:00 List-Id: > 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. 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.