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=-0.8 required=5.0 tests=BAYES_00,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!uunet!husc6!mit-eddie!ll-xn!cit-vax!ucla-cs!zen!ucbvax!SIERRA.STANFORD.EDU!Mendal
From: Mendal@SIERRA.STANFORD.EDU (Geoff Mendal)
Newsgroups: comp.lang.ada
Subject: Re: All possible results?
Message-ID: <12331994725.14.MENDAL@Sierra.Stanford.EDU>
Date: Fri, 4-Sep-87 15:50:15 EDT
Article-I.D.: Sierra.12331994725.14.MENDAL
Posted: Fri Sep  4 15:50:15 1987
Date-Received: Sat, 5-Sep-87 19:48:36 EDT
References: <ie53%NTSUVAX.BITNET@wiscvm.wisc.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

"accepted" must be printed no matter what implementation the
program is executed on.  TASKING_ERROR cannot occur as a result
of kill calling t.a (at least, not in this simple program).

The semantics of the terminate alternative guarantee that the task
(task a) cannot complete while any other task (in this case, the
thread of control executing procedure kill) can call one of a's
entries.  For details, read RM 9.4 and 9.7.1(10).

gom
-------