Re: Task Discriminants & Arrays

["John G. Volan" <johnvolan@sprintmail.com>]

Sorry, I should have added the following:

John G. Volan wrote:
> 
> Robert A Duff wrote:
>
> > Sorry, I don't get it.  Are you saying "this is a mess"?  Yeah, it is.
> > Shrug.
> 
> No, no! I think this is a great solution!

Of course, you should wrap a nice abstraction around this.  All that a
user should have to know is that there are these tasks and they are
accessible by id number:

  package Processes is

    type Process_Id_Type is range ...;

    function Get_New_Process_Id return Process_Id_Type;

    task type Process_Type
      (Process_Id : Process_Id_Type := Get_New_Process_Id)
    is
      ...
    end Process_Type;

    type Process_Access_Type is access all Process_Type;

    function Get_Process
      (Process_Id : in Process_Id)
       return Process_Access_Type;

    -- Note to clients: To get access to a Process_Type task, call
    -- Get_Process. DO NOT declare any Process_Type tasks
    -- of your own; this will result in Constraint_Error.
    -- Elaboration of this package already results in the creation
    -- of one task for each value in Process_Id_Type.

  end Processes;

------------------------------------------------------------------------
Internet.Usenet.Put_Signature 
  (Name => "John G. Volan",  Home_Email => "johnvolan@sprintmail.com",
   Slogan => "Ada95: The World's *FIRST* International-Standard OOPL",
   Disclaimer => "These opinions were never defined, so using them " & 
     "would be erroneous...or is that just nondeterministic now? :-) ");
------------------------------------------------------------------------