Re: timer_server triggers Task_Termination handler

[Georg Bauhaus <bauhaus@futureapps.invalid>]

On 21.04.16 23:26, Robert A Duff wrote:
> Per Dalgas Jakobsen <pdj@knaldgas.dk> writes:
>
>> Is it correct behaviour when tasks internal to the GNAT run-time causes
>> users task_termination handlers to be called?
>
> No.  Internal tasks are an implementation detail, and should be
> invisible to Ada programs.

Should whatever the Ada program includes from the run-time
have hidden effects only? Inaccessible in a black box, with
thick walls, and no outlets?

> I fixed this bug in GNAT recently.
>

 From Randy's response, I understand that "bug" might be only one
reading. Suppose that program development needs to trace hardware
utilization, or generally the life of _all_ task objects. Should this
not be available using some standard mechanism?

ALL(x)[x is task_termination -> x is event]

     changed to mean

ALL(x)[x is task_termination ->
          x'task visible in the program -> x is event]

revokes access to all source-invisible run-time effects, or events.
A registration scheme more flexible than ALL vs ALL that you know about,
or ALL that we choose for you, seems another reading more open to
project needs.