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,2876a344d1b6d2ae,start X-Google-Attributes: gid103376,public From: "W. Wesley Groleau (Wes)" Subject: Problem with measuring time. Date: 1996/12/04 Message-ID: <9612042145.AA16228@most>#1/1 X-Deja-AN: 202497413 sender: Ada programming language comments: Gated by NETNEWS@AUVM.AMERICAN.EDU mailer: Elm [revision: 70.85] newsgroups: comp.lang.ada Date: 1996-12-04T00:00:00+00:00 List-Id: Does any one know a way to meet the following requirements (who is able and willing to share it)? 1. Works on HP RISC 2. In C and/or Ada 83. 3. Measures time intervals of up to 6 hours with "reasonable" accuracy* 4. Will not interfere with the Alsys 5.5.2A runtime 5. Low overhead 6. NOT affected by another Unix process changing the clock via date(1) or settimeofday(2) 7. Does not require any hardware changes. * reasonable = better than what we have now :-) Borrowing the GNAT code for Ada.Real_Time.Clock will not meet requirement #6 (already tried that one). --------------------------------------------------------------------------- W. Wesley Groleau (Wes) Office: 219-429-4923 Hughes Defense Communications (MS 10-40) Home: 219-471-7206 Fort Wayne, IN 46808 (Unix): wwgrol@pseserv3.fw.hac.com ---------------------------------------------------------------------------