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,ab2ba9c5d12b0f12
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Concurrency in Gnat 3.05?
Date: 1996/07/20
Message-ID: <dewar.837877693@schonberg>#1/1
X-Deja-AN: 169089271
references: <4sjqte$3mu@masala.cc.uh.edu> <qw63f2qou73.fsf@gargantua.enst.fr>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-07-20T00:00:00+00:00
List-Id: <comp.lang.ada>


Samuel Tardieu said, replying to spasmo

Spasmo> Is Gnat 3.05 (for DOS) truly concurrent when executing tasks?

AFAIK it's not, but there is nothing in the RM that requires it !


On the contrary, there *is* something in the RM that prohibits it! See
annex D. The default FIFO_Within_Priorities scheduling policy requires
run-till-blocked, and time slicing (which is what we are talking about here)
violates that important requirement!

Of course it is fine to have alternative scheduling policies, but this is
implementation dependent, and an implementation that does not support
the real time annex may indeed implement time slicing by default.