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,d5977aa20216d24a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-04 09:41:44 PST Path: supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!newsfeed.berkeley.edu!ucberkeley!sjc1.nntp.concentric.net!newsfeed.concentric.net!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: Ada Tasks vs Linux processes References: <3AC8FA76.C6AD4B53@boeing.com> X-Newsreader: Tom's custom newsreader Message-ID: Date: Wed, 04 Apr 2001 16:36:52 GMT NNTP-Posting-Host: 24.20.190.201 X-Complaints-To: abuse@home.net X-Trace: news1.frmt1.sfba.home.com 986402212 24.20.190.201 (Wed, 04 Apr 2001 09:36:52 PDT) NNTP-Posting-Date: Wed, 04 Apr 2001 09:36:52 PDT Organization: Excite@Home - The Leader in Broadband http://home.com/faster Xref: supernews.google.com comp.lang.ada:6459 Date: 2001-04-04T16:36:52+00:00 List-Id: > ... by delaying until the next clock tick. Note this is a change from Ada 83, where the delay had to be "at least" that specified. Suppose there's a piece of hardware that needs 500 mics to settle after some operation, before it can next be accessed. Given a Duration'small of 10*mics, the unsuspecting programmer might write "delay 500*mics;". With a System.Tick of 1000 mics, that would delay somewhere between 1 and 2 ms, a safe time for the hardware to settle down, when compiled with Ada 83. In Ada 95 it need only take a single tick, which might happen within a few mics of reaching the "delay" statement and thus long before the hardware is ready. Crash and burn.