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!uunet!husc6!mit-eddie!ll-xn!cit-vax!ucla-cs!zen!ucbvax!NTSUVAX.BITNET!ie53
From: ie53@NTSUVAX.BITNET (HAERIM LEE)
Newsgroups: comp.lang.ada
Subject: All possible results?
Message-ID: <8709041817.AA10351@ucbvax.Berkeley.EDU>
Date: Fri, 4-Sep-87 14:48:38 EDT
Article-I.D.: ucbvax.8709041817.AA10351
Posted: Fri Sep  4 14:48:38 1987
Date-Received: Sat, 5-Sep-87 18:38:53 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

-- What are all possible results of the execution of the following
-- code on BOTH a single processor system and a multi-processor system?
-- Can an exception 'TASKING_ERROR' be raised at (***)?  Or will "accepted"
-- be ALWAYS printed on the screen?  Or sometimes printing "accepted" and
-- sometimes raising 'TASKING_ERROR' will occur?  Please consider BOTH
-- systems mentioned above.  Send any comments to IE53@NTSUVAX.

with text_io; use text_io;
procedure kill is
  task a is
    entry e;
  end a;
  task body a is
  begin
    select
        accept e do
          put_line("accepted");
        end e;
    or
        terminate;
    end select;
  end a;
begin
  a.e;          -- ***
end kill;