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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f8311a3a7edd715 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2000-12-19 21:29:56 PST Path: supernews.google.com!sn-xit-02!supernews.com!216.218.236.179.MISMATCH!news!news.he.net!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!news1.frmt1.sfba.home.com.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Using "delay until" in real-time References: <91p98c$49d$1@nnrp1.deja.com> X-Newsreader: Tom's custom newsreader Message-ID: Date: Wed, 20 Dec 2000 05:29:54 GMT NNTP-Posting-Host: 24.20.190.201 X-Complaints-To: abuse@home.net X-Trace: news1.frmt1.sfba.home.com 977290194 24.20.190.201 (Tue, 19 Dec 2000 21:29:54 PST) NNTP-Posting-Date: Tue, 19 Dec 2000 21:29:54 PST Organization: Excite@Home - The Leader in Broadband http://home.com/faster Xref: supernews.google.com comp.lang.ada:3277 Date: 2000-12-20T05:29:54+00:00 List-Id: >is that "n" is a counter that has to be monotonically increasing. That >means that it will eventually hit an archetectural limit. Of course on >my 32-bit machine at 240Hz that limit won't happen until the machine has >been running for about 1/3 of a year, but the limit is there. That suggests "n" is 32 bits. Will your compiler support a larger integer? Or perhaps a "type counter is delta 1.0 range 0.0 .. 2.0**63;" Anything that counts or sums must eventually overflow. If Real_Time.Time doesn't overflow during your program's lifespan then it either increments less often or has more bits.