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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,b4731a3b5d591abd
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Task Discriminants & Arrays
Date: 1997/05/15
Message-ID: <EA8n1w.Hvn@world.std.com>#1/1
X-Deja-AN: 241780393
References: <mheaney-ya023680001305970024550001@news.ni.net>
 <3379C86F.352@this.message> <EA800I.Dv2@world.std.com>
 <337B09C9.62BB@sprintmail.com>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1997-05-15T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <337B09C9.62BB@sprintmail.com>,
John G. Volan <johnvolan@sprintmail.com> wrote:
>  task type Process_Type
>    (Process_Id : Process_Id_Type := Get_New_Process_Id)
>     -- Note: We have to make sure this function is already
>     -- elaborated at this point; probably needs to be in another
>     -- package

Not at *this* point.  Just before you create any objects of this type.

>  is
>    ...
>  end Process_Type;
>
>  type Process_Access_Type is access all Process_Type;
>
>  type Process_Array_Type is
>    array (Process_Index_Type range <>) of aliased Process_Type;
>    -- Note: Process_Index_Type does not necessarily have to be
>    -- the same as Process_Id_Type.  In fact, they probably should
>    -- be different to avoid confusing the id of a process with its
>    -- arbitrary location in such an array, which won't necessarily
>    -- be the same.

Good point.

>    Process_Array : aliased Process_Array_Type (1 .. 1E6);
>    -- Wham!! ... all activated at once

Yeah, right.  A million tasks.

>...
>  end Jeff_Carters_Million_Processes;
>
>:-) :-) :-)

Sorry, I don't get it.  Are you saying "this is a mess"?  Yeah, it is.
Shrug.

- Bob