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.1 required=5.0 tests=BAYES_20,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!MITRE-BEDFORD.ARPA!cb
From: cb@MITRE-BEDFORD.ARPA (Christopher Byrnes)
Newsgroups: net.lang.ada
Subject: Re: Runtime behavior of Ada tasks
Message-ID: <8609241248.AA23792@mitre-bedford.ARPA>
Date: Fri, 26-Sep-86 09:18:56 EDT
Article-I.D.: mitre-be.8609241248.AA23792
Posted: Fri Sep 26 09:18:56 1986
Date-Received: Fri, 26-Sep-86 21:07:19 EDT
References: <8609240638.AA16811@mitre-bedford.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The MITRE Corp., Bedford, MA
List-Id: <comp.lang.ada>


  Check 9.8(5) of the Ada* LRM.  It states that "For tasks of the same
priority, the scheduling order is not defined by the language.  For tasks
without explicit priority, the scheduling rules are not defined..."  Your
Ada compiler's runtime system is allowed to do almost anything with the
output from your two tasks (in terms of interleaving, starvation, etc.).
If you want the output from your two tasks to be periodicly switched back
and forth between the tasks, you'll have to program it that way.

					Christopher Byrnes
					The MITRE Corporation
					Burlington Road
					M/S A425
					Bedford, Mass. 01730

					cb@Mitre-Bedford.ARPA
					...!decvax!linus!mbunix!cb.UUCP
* Ada is a trademark of the Ada Joint Program Office