Re: Strange warning message

[Simon Wright <simon@pushface.org>]

Robert Eachus <rieachus@comcast.net> writes:

> For tasks, we have this additional constraint.  You can't leave the
> scope in which a task is declared because the task can still access
> those objects.  So functions, procedures, tasks and even packages can
> need to wait for all the tasks declared locally to be completed (or
> waiting at a terminate alternative).  Again declaring library level
> tasks, if you don't need this complex behavior, eliminates run-time
> code to make it work.

In my experience, when GNAT (with the default static elaboration) has
been unable to find a valid elaboration order, it's almost always been
because of library-level tasks; the binder can't tell whether the task
(which starts executing on completion of its package's elaboration)
actually makes any calls to with'd packages at that point, so assumes
the worst.