From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: timer_server triggers Task_Termination handler Date: Fri, 22 Apr 2016 15:42:03 +0200 Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: G7MXAklp0OAVRSdfcmpxRQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:30244 Date: 2016-04-22T15:42:03+02:00 List-Id: On 22/04/2016 15:33, G.B. wrote: > On 22.04.16 14:55, Dmitry A. Kazakov wrote: >> The point is that it must be your scheduler to make sense. You scheduler >> will be able to know that. > > What does "your" stand for and what ownership relation exists > between the program, the scheduler (whose), and run-time tasks' > termination events? The schedule is the master of these tasks. The point is that events must be reported to the task's master. That eliminates the problem of ambiguity which tasks, threads, services, drivers, interrupts, embedded procedures, co-routines etc must generate events. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de