Re: Elaboration Order

[Simon Wright <simon@pogner.demon.co.uk>]

Robert Dewar <robert_dewar@my-deja.com> writes:

> Another issue has to do with tasks. It is generally risky to
> have library tasks starting at elaboration time, since it
> means that you have arbitrary code running before the main
> package elaboration is complete. If you create such tasks,
> you must very carefully review them to make sure that they
> do not cause elaboration problems.

And your compiler (well, binder) may not be able to tell whether there
is an elaboration problem or not; _you_ may know that the task only
makes a problematic call after it has been allowed to start via some
rendezvous, which won't happen until the whole program has elaborated,
but the _compiler_ may not.

The cases where I've had this problem have both felt a bit
unsatisfactory when I reviewed the design.