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,e8e240cec570cdf2 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-19 14:53:31 PST Newsgroups: comp.lang.ada Path: supernews.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed1.edgix.com!uunet!ash.uu.net!world!bobduff From: Robert A Duff Subject: Re: Multiple entry tasks Sender: bobduff@world.std.com (Robert A Duff) Message-ID: Date: Thu, 19 Apr 2001 21:52:15 GMT References: <9bkevj$61k$1@nh.pace.co.uk> <9bkqud$a5b$1@nh.pace.co.uk> Organization: The World Public Access UNIX, Brookline, MA X-Newsreader: Gnus v5.3/Emacs 19.34 Xref: supernews.google.com comp.lang.ada:7021 Date: 2001-04-19T21:52:15+00:00 List-Id: "Marin David Condic" writes: > Cascading the selects is an interesting mechanism. I'm not sure there is any > answer that will be definitive. (Short of a language mod allowing one to > prioritize entries?) Under the Priority_Queueing policy, the entries are prioritized -- you write the higher-priority accepts before the lower-priority ones. Task priorities take precedence over entry priorities, however. I'm not sure whether that's what the original poster wanted, but if all the tasks are the same priority, then the order of the accept statements determines the priority of the entries. See RM-D.4(14). - Bob