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.2 required=5.0 tests=BAYES_00,FROM_WORDY, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5f0b2f174ad085de X-Google-Attributes: gid103376,public From: "Nick Roberts" Subject: Re: tasking in Ada and Annex D question Date: 1999/02/03 Message-ID: <798u7r$b2k$2@plug.news.pipex.net>#1/1 X-Deja-AN: 440097174 References: <793jl9$hf@drn.newsguy.com> <7963h1$a6h$1@nnrp1.dejanews.com> <797hoc$j3v$1@nnrp1.dejanews.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Organization: UUNET WorldCom server (post doesn't reflect views of UUNET WorldCom) Newsgroups: comp.lang.ada Date: 1999-02-03T00:00:00+00:00 List-Id: To quote chapter and verse, RM95 D.2.2 [7] states ... The language defines only one dispatching policy, FIFO_Within_Priorities; when this policy is in effect, modifications to the ready queues occur only as follows ... with the emphasis on "only", the list that follows this clause does not include any timed pre-emption. It does, however, include the 'delay' statement, so (as another poster mentioned, I think), if you pop in a 'delay 0.0;' statement just after (say) the I/O operation, you'll get a nice alternation of task activation. ------------------------------------------- Nick Roberts ------------------------------------------- robert_dewar@my-dejanews.com wrote in message <797hoc$j3v$1@nnrp1.dejanews.com>... [...] |Well I am of course talking about |FIFO_Within_Priorities. If you don't specify |the dispatching policy, then of course it is |undefined. | |But FWP is the only defined policy in the RM, |and it most definitely requires run till blocked |(and whether IO is blocking or not is of course |implementation defined).