Re: Termination of periodic tasks

["Randy Brukardt" <randy@rrsoftware.com>]

"Jeffrey Carter" <spam.jrcarter.not@spam.not.acm.org> wrote in message 
news:lnpvb7$oat$3@dont-email.me...
> 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.

That's certainly true for this code as written, but there is a way to write 
the code so it will terminate. See my other message.

Note that you need both methods if you want to allow the objects to be 
declared anywhere: finalization for objects in nested scopes, and the 
Is_Callable trick for those declared at library-level.

                                   Randy.