Re: Task deallocation

["Jonas Nygren" <ehsjony@ehs.ericsson.se>]

I sent out a question about how to deallocate dynamically allocated tasks.
There were some answers from which I learnt that deallocating new'd tasks
was perhaps not so straightforward as I believed. 

Apparently most compilers represents a task by a pointer to some internal
structure. If this internal storage is not reclaimed when a task is 
deallocated one will have a storage leak. 

So my question is how to deallocate a dynamically allocated task without
creating a memory leak. 

If I call Free for a dynamically allocated task will this ensure that the
internal storage structures for tasks are reclaimed? E.g.:

	type My_Task_Ref is access My_Task;
	procedure Free is new Unchecked_Deallocation(My_Task, My_Task_Ref);
	MTR : My_Task_Ref := new My_Task;
	...
	Free(MTR); -- assume MTR'Terminated is true
	-- will the internal task structures have been reclaimed??

or will it just reclaim the pointer that the compiler use to represent 
the instance of My_Task.

My guess is that the example above will result in a storage leak. Mats
Weber 
suggested that the only portable solution to handle deallocation of tasks 
is to put them on a global free-list instead of deallocating them.

Is there really no portable way to deallocate dynamically allocated tasks 
without storage leaks? 

/jonas