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.9 required=5.0 tests=BAYES_50,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!cca!mirror!ishmael!ada-uts!fitch
From: fitch@ada-uts
Newsgroups: comp.lang.ada
Subject: Re: can not abort allocated tasks
Message-ID: <57900047@ada-uts>
Date: Mon, 12-Oct-87 09:27:00 EDT
Article-I.D.: ada-uts.57900047
Posted: Mon Oct 12 09:27:00 1987
Date-Received: Sat, 17-Oct-87 04:23:25 EDT
References: <7586@steinmetz.steinmetz.UUCP>
Nf-ID: #R:steinmetz.steinmetz.UUCP:-758600:ada-uts:57900047:000:450
Nf-From: ada-uts!fitch    Oct 12 09:27:00 1987
List-Id: <comp.lang.ada>


By using ".all" you can refer to a task object via a pointer.
So you want to specify

    abort POOL_1.all;
    
If, however, this task does have an infinite loop, your abort
may not help you, since an "aborted" task may not become
completed until it hits a syncronization point, e.g. an accept
statement. Better to remove the loop and using a less severe
method to stop the task.

Geoff Fitch
Intermetrics, Inc.
733 Concord Ave.
Cambridge, MA 02138