Re: How to tell whether program finalization can be suppressed

[Robert Eachus <rieachus@comcast.net>]

On Monday, December 4, 2017 at 6:58:48 AM UTC-5, AdaMagica wrote:
> Am Sonntag, 3. Dezember 2017 18:16:47 UTC+1 schrieb Robert Eachus:
> > On Saturday, December 2, 2017 at 6:12:13 AM UTC-5, AdaMagica wrote:
> > > 
> > > Just to refresh my memory:
> > > The main subprogram is the master of any library tasks. It may be empty (I just confirmed this with a little test) and thus does not exit until all library tasks are terminated or waiting on a terminate alternative.
> > > 
> > > with Lib;  -- in the elaboration sequence, there are some tasks
> > > procedure Main is
> > > begin
> > >   null;  -- waiting here for tasks to terminate
> > > end Main;
> > 
> > No, the environment task is the master of library level tasks...
> 
> But that's what Randy wrote:
> "When the main program exits, of course the environment task completes and then
> terminates. It's the completion of the environment task that starts library-level finalization."
> So what did he want to say? Main resp. env task exits, completes, terminates... Normally, Randy is precise in what he says.

I wasn't disagreeing with Randy, except maybe to make it clearer that library level tasks can continue to run after the main program completes.  I was disagreeing with your statement that the main program is the master of library-level tasks.  Didn't matter in your example, but I could probably gin up an example.  Hmm.  Something with Ada.Text_IO.File_Types and reassignment of Current_Output? I usually keep the main program around to print out a message when the program completes successfully, but that's personal style.