From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 20 Jul 91 00:38:20 GMT
From: eachus@mitre-bedford.arpa  (Robert I. Eachus)
Subject: Re: Task Access Type Variables
Message-ID: <EACHUS.91Jul19173820@largo.mitre.org>
List-Id: <comp.lang.ada>

In article <9107181212.aa26405@PARIS.ICS.UCI.EDU> jduarte@liege.ICS.UCI.EDU (J 
o s e D u a r t e) writes:

	   What happens to the value of a variable which
   is an access to a task (type) once the task completes
   its job or terminates for some reason?

	   Does this access type variable become NULL or
   will it access some garbage location?

   The task object must stay around until the scope of the access type
is left, so that the attributes work and calls return the correct
exception.  (There is one special case that the ARG has decided is
pathological...  You can return a task from a function which in Ada
terms is its master.  But this pathology doesn't involve access
types.)


					Robert I. Eachus

with STANDARD_DISCLAIMER;
use  STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...
--

					Robert I. Eachus

with STANDARD_DISCLAIMER;
use  STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...