Re: Task activation

[tonyg <tonythegair@gmail.com>]

On Dec 21, 12:35 pm, Niklas Holsti <niklas.hol...@tidorum.invalid>
wrote:
> On 11-12-21 13:58 , tonyg wrote:
>
>
>
> > I seem to have a problem with task activation
>
> > I have a task which I am using to launch other tasks. This task is
> > activating fine. I have three task pointers in a package spec, when I
> > want to activate the task I declare a task of the necessary type
> > inside a procedure and point the access variable to the task. However
> > it does not seem to get past activation of the task. I cannot see the
> > reason for this.
>
> If you declare a task as a local object within a procedure, the
> procedure cannot return until the task is completed. The procedure will
> wait at its "end" for all its local tasks to finish.
>
> If you want to create a task in a procedure in such a way that the task
> continues to exist and run after the procedure returns, you must make
> the procedure allocate a new task object, from the heap, with a "new".
>
> --
> Niklas Holsti
> Tidorum Ltd
> niklas holsti tidorum fi
>        .      @       .

My apologies , the information I supplied was sketchy. My problem (or
challenge :) )
was resolved by using the pragma elaborate_all on my 'with's of the
packages containing
the tasks.