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,5f0b2f174ad085de X-Google-Attributes: gid103376,public From: robert_dewar@my-dejanews.com Subject: Re: tasking in Ada and Annex D question Date: 1999/02/02 Message-ID: <7963h1$a6h$1@nnrp1.dejanews.com>#1/1 X-Deja-AN: 439641730 References: <793jl9$hf@drn.newsguy.com> X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I) X-Http-Proxy: 1.0 x15.dejanews.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Tue Feb 02 05:47:15 1999 GMT Newsgroups: comp.lang.ada Date: 1999-02-02T00:00:00+00:00 List-Id: In article <793jl9$hf@drn.newsguy.com>, nabbasi@earthlink.net wrote: > 1. How could FSU be an Annex D compliant, if one thread > will block the other like this? (even though one will > expect that doing an IO message will cause a task to > yield the CPU). Annex D requires run till blocked semantics, and forbids any kind of time slicing. You say that you "expect" that doing an IO message will cause a task to yield the CPU. You can expect anything you like, but you read no such requirement in the RM, because there is no such requirement! -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own