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,d4bb9272b7314785 X-Google-Attributes: gid103376,public From: "Corey Ashford" Subject: Re: ObjectAda - no clock drift! Date: 1998/06/17 Message-ID: <6m7r5m$4gn$1@usenet.rational.com>#1/1 X-Deja-AN: 363444045 References: <6m6f0t$1ue$1@nnrp1.dejanews.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Organization: Rational Software Newsgroups: comp.lang.ada Date: 1998-06-17T00:00:00+00:00 List-Id: dennison@telepath.com wrote in message <6m6f0t$1ue$1@nnrp1.dejanews.com>... >Apparently, Aonix has made atomic clocks obsolete with the simple use of a >Wintel PC. > >The Ada rm in D.8 paragraph 41-43 requires vendors to give "an upper bound on >the drift rate of Clock with respect to real time." I was curious what my >Aonix ObjectAda compiler said, so I looked it up. > >The documentation Requirements section of the ObjectAda 7.1 NT docs (p 2-9) >has the following statement: There is no software clock drift. > >What is meant by this? Surely not what I think it's saying! I think it's saying that the way the software is written, it will not cause the current time to drift as a side-effect of the way it keeps time the way some algorithms do. However, if the hardware clock drifts, it has no control over that. - Corey