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_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.66.182.130 with SMTP id ee2mr3455805pac.37.1404841852661;
 Tue, 08 Jul 2014 10:50:52 -0700 (PDT)
X-Received: by 10.182.225.162 with SMTP id rl2mr90475obc.13.1404841852369;
 Tue, 08 Jul 2014 10:50:52 -0700 (PDT)
Path: 
 border2.nntp.dca1.giganews.com!nntp.giganews.com!uq10no216483igb.0!news-out.google.com!gf2ni1igb.0!nntp.google.com!hn18no387708igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 8 Jul 2014 10:50:51 -0700 (PDT)
In-Reply-To: <CvVuv.204762$bA1.17573@fx22.iad>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=149.32.224.35;
 posting-account=Qh2kiQoAAADpCLlhT_KTYoGO8dU3n4I6
NNTP-Posting-Host: 149.32.224.35
References: <e17758fe-b230-4ef6-b144-d5a68e821915@googlegroups.com>
 <lyk37peh77.fsf@pushface.org>
 <35cd9c91-4b2c-4baa-9ef6-3c69fd7086ce@googlegroups.com>
 <CvVuv.204762$bA1.17573@fx22.iad>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <83fe939e-baed-4656-9aa9-1c7c8c5d9d05@googlegroups.com>
Subject: Re: Protected Type compiler complaint
From: Anh Vo <anhvofrcaus@gmail.com>
Injection-Date: Tue, 08 Jul 2014 17:50:52 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: number.nntp.dca.giganews.com comp.lang.ada:187460
Date: 2014-07-08T10:50:51-07:00
List-Id: <comp.lang.ada>

On Tuesday, July 8, 2014 10:03:31 AM UTC-7, Shark8 wrote:
> On 07-Jul-14 08:23, NiGHTS wrote:
> > A question about the variables in the Test.P type you introduced. 
> > I would like to make available to other spawned tasks these protected 
> > variables, so essentially Test.P needs to be a global of some kind 
> > with static data in the currently running process. 
> 
> Not necessarily; you could use an access-discriminated task for these  
> spawned tasks.

The term spawned tasks makes me think low level OS tasks are involved here. Actually, it is just a regular Ada task. Thus, I would simply call it task(s) :-)