Re: DYNAMIC ADA TASK CREATION?

[Georg Bauhaus <sb463ba@d2-hrz.uni-duisburg.de>]

Robert I. Eachus <rieachus@attbi.com> wrote:
: Simon Wright wrote:
: 
:> (uncompiled)
:> 
:>   task type t is
:>     --  some entries
:>   end t;
:> 
:>   task body t is
:>   begin
:>     --  code
:>   end t;
:> 
:>   type ts is array (positive range <>) of t;
:> 
:>   n : positive;
:> 
:> begin
:> 
:>   --  read in n  
:> 
:>   declare
:>     the_ts : ts (1 .. n);
:>   begin
:>     --  do something with the tasks
:>     --  NB, can't pass this point until all the tasks have terminated
:>   end;
: 
: Correct.  But if you don't want to get stuck there, do this instead:
: 
:     -- task type t as above
:     type ta is access t;
: 
:     type ts is array (positive range <>) of ta := new t;
                                                 ^^^^^^^^  
I think I got the idea and made me program to see the tasks working
outside the declare block. A good hint!
But is new t on the line above some new default initialisation
construct, or meant to abbreviate something? (The compiler complains.)
: 
 [...]
: 
:     declare
:       the_ts : ts (1 .. n);
:     begin
:       --  do something with the tasks
:       --  NB, CAN pass this once all the tasks have been created.
:     end;
: 
: For an ordinary task object, the creator of the object is the master (in 
: the original example, a declare block.  But for a task created by an 
: allocator, the place where the access type was declared determines who 
: is the master.  (In either case, if that is in a library package, the 
: master is the environment task.)
: 

--  Georg