Re: Freeing access-to-task objects

[Emmanuel Briot <briot.emmanuel@gmail.com>]

I did not mention it in the blog, but we also like running with the restriction No_Task_Hierarchy (which generates slightly more efficient code, at least in older versions of GNAT if I understand correctly the reasons we have it). So the declare block approach doesn't work, this is one of the big reasons for using access-to-task, too.

Waiting for exceptions is one possibility, though I dislike it because this is using exceptions for what is the normal flow of the program. They also make debugging more complicated.

The active loop is not the best solution, but it isn't very costly in practice. The task terminates fairly soon (depending on the load on the machine), and we could possibly use a delay like 1.0 if we basically want the active loop.