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: 
 border2.nntp.dca3.giganews.com!backlog4.nntp.dca3.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Jeffrey Carter <spam.jrcarter.not@spam.not.acm.org>
Newsgroups: comp.lang.ada
Subject: Re: Termination of periodic tasks
Date: Tue, 17 Jun 2014 10:53:42 -0700
Organization: Also freenews.netfront.net; news.tornevall.net;
 news.eternal-september.org
Message-ID: <lnpvb7$oat$3@dont-email.me>
References: <slrnlpqs89.i0l.lithiumcat@nat.rebma.instinctive.eu>
 <lnkj3d$jkf$1@dont-email.me>
 <slrnlptu84.i0l.lithiumcat@nat.rebma.instinctive.eu>
 <lnn8bb$i9s$1@dont-email.me>
 <slrnlpvpmv.i0l.lithiumcat@nat.rebma.instinctive.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 17 Jun 2014 17:53:44 +0000 (UTC)
Injection-Info: mx05.eternal-september.org;
 posting-host="ba346f17b503f6aa8ecbfd6d1e2a9f59";
 logging-data="24925"; mail-complaints-to="abuse@eternal-september.org";
 posting-account="U2FsdGVkX18VUnA1/IvHXX2CmGCuhXcWY2nzfxdd28A="
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
In-Reply-To: <slrnlpvpmv.i0l.lithiumcat@nat.rebma.instinctive.eu>
Cancel-Lock: sha1:pynQzcqCTdy8FAOJ6Ral6d2D91A=
X-Original-Bytes: 2186
Xref: number.nntp.dca.giganews.com comp.lang.ada:187023
Date: 2014-06-17T10:53:42-07:00
List-Id: <comp.lang.ada>

On 06/16/2014 11:57 PM, Natasha Kerensikova wrote:
>
> Now the master of Global_Entry is also the environment task. So
> Global_Entry will not be finalized before the worker task terminates,
> but by design the worker task will not terminate before Global_Entry is
> finalized or Reset.
>
> So unless at some point Global_Entry.Reset is called, this package will
> cause the program to never terminate.
>
> Is there a way to work around such a situation? Or should I just
> document this as a caveat (among many others, as you can see at the
> beginning of the spec)?

AFAICT, there is no way for this situation to terminate without outside 
intervention.

-- 
Jeff Carter
"Saving keystrokes is the job of the text editor,
not the programming language."
Preben Randhol
64