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:35:06 -0500 Organization: JSA Research & Innovation Message-ID: References: NNTP-Posting-Host: rrsoftware.com X-Trace: loke.gir.dk 1461364507 27093 24.196.82.226 (22 Apr 2016 22:35:07 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Fri, 22 Apr 2016 22:35:07 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Xref: news.eternal-september.org comp.lang.ada:30250 Date: 2016-04-22T17:35:06-05:00 List-Id: "Robert A Duff" wrote in message news:wcca8kmac15.fsf@TheWorld.com... > Per Dalgas Jakobsen 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. Nice thought, but exactly the opposite to some of opinions in the e-mail associated with the design of the task termination feature. They wanted to be notified if an internal task failed (presumably to narrow down the cause of the inevitable failure cascade that follows). Given the Ada definition, it is wrong to hide an Ada task. Of course, there is no reason to use Ada tasks in the runtime (the runtime could be written C or Prolog ;-), so there is no truely wrong answer here. Randy.