From: eachus@mitre-bedford.arpa (Robert I. Eachus)
Subject: Re: Task Access Type Variables
Date: 20 Jul 91 00:38:20 GMT [thread overview]
Message-ID: <EACHUS.91Jul19173820@largo.mitre.org> (raw)
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...
next reply other threads:[~1991-07-20 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-07-20 0:38 Robert I. Eachus [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-07-19 14:30 Task Access Type Variables Jean Pierre Rosen
1991-07-19 13:22 Norman H. Cohen
1991-07-18 21:03 J o s e D u a r t e
1991-07-18 19:12 J o s e D u a r t e
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox