Article View: net.lang.ada
Article #963Sharing processor between tasks.
From: "BUD::PEARSON"
Date: Wed, 24 Sep 1986 15:55
Date: Wed, 24 Sep 1986 15:55
14 lines
1251 bytes
1251 bytes
Somebody in UK-land with an address much too long to work asks why his program, which defines two free-running tasks that do nothing but print distinctive messages, prints only one of the two kinds of messages. The answer is simply that Ada doesn't promise to time-slice tasks of the same priority. LRM 9.8 says: "For tasks of the same priority, the scheduling order is not defined by the language." DEC's VAX Ada seems to follow the strategy of executing one task until it becomes unrunnable or until a task of higher priority becomes runnable. Makes sense. - Peter (pearson%anchor.decnet@lll-icdc.arpa) ------
Technical Details
Message-ID:
<8609242042.AA26495@ucbvax.Berkeley.EDU>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!LLL-ICDC.ARPA!pearson%bud.DECnetShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!LLL-ICDC.ARPA!pearson%bud.DECnet
From: pearson%bud.DECnet@LLL-ICDC.ARPA ("BUD::PEARSON")
Newsgroups: net.lang.ada
Subject: Sharing processor between tasks.
Message-ID: <8609242042.AA26495@ucbvax.Berkeley.EDU>
Date: Wed, 24-Sep-86 11:55:00 EDT
Article-I.D.: ucbvax.8609242042.AA26495
Posted: Wed Sep 24 11:55:00 1986
Date-Received: Wed, 24-Sep-86 22:23:55 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "BUD::PEARSON" <pearson%bud.decnet@lll-icdc.arpa>
Organization: The ARPA Internet
Lines: 14