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!gandalf.srv.welterde.de!news.jacob-sparre.dk!loke.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: timer_server triggers Task_Termination handler Date: Fri, 22 Apr 2016 17:31:01 -0500 Organization: JSA Research & Innovation Message-ID: References: NNTP-Posting-Host: rrsoftware.com X-Trace: loke.gir.dk 1461364262 28238 24.196.82.226 (22 Apr 2016 22:31:02 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Fri, 22 Apr 2016 22:31:02 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Xref: news.eternal-september.org comp.lang.ada:30249 Date: 2016-04-22T17:31:01-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:nfcjmm$1nei$1@gioia.aioe.org... ... > I think it should be the task's master to which all task events are > reported. The master can propagate them further. That's how general termination handlers work. In this case, the "master" is the environment task, which is the master of all tasks in the Ada program (recall that masters are nested, most tasks belong a number of masters). The question here is whether the Ada implementer should be deciding that some tasks should be excluded from such reporting. Randy.