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,37ba7a408adb23df
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Confused About Task Priorities (Ada 83)
Date: 1998/02/26
Message-ID: <dewar.888547874@merv>#1/1
X-Deja-AN: 329016277
References: <1998Feb25.230411.14969@nosc.mil>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 888548088 24724 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-02-26T00:00:00+00:00
List-Id: <comp.lang.ada>


Charles asks about the effect of priorites in Ada 83. You really cannot
say anything very definite about the semantics of a tasking program in
Ada 83. Priorities are only used to indicate urgency of a task, and it
is perfectly valid for example to time slice between different tasks
on the grounds that e.g. you are simulating a multi-processor.

I would say that the behavior you are seeing is odd, but not non-conforming
in Ada 93. If you want predictable scheduling behavior, use an Ada 95
compiler that implements Annex D.