Re: Function Calls by Address

["Robert I. Eachus" <eachus@mitre.org>]

Robert A Duff wrote:
 
> I don't understand the elaboration order issue.  The rules are that the
> elaboration or is *exactly* as if you move all the with_clauses from the
> subunits up to the containing library unit.  So that part is easy.

     I finally see what you are talking about.  Subunits allow you to
create a program which will raise Program_Error or some other exception
at run-time.  Of course you can use pragma Suppress(Elaboration_Check)
to prevent this where you KNOW that the elaboration rules are too
conservative, but I don't recommend this.  Or you could complete all
your work before the main program is called...  However, in Ada there
are usually many legal compilation orders for such programs--if subunits
are used to minimize the number of with_clauses on any unit.

    Now assume you need to do maintenance on a program that is near the
edge, or more likely you are reusing such software.  If elaboration
checks were done at compile time, you would have a great deal of
difficulty making the changes.  (In other languages you could make the
changes, but with no assurance that the result would run correctly.) 
Almost any change would require recompiling everything.  The net result
would be that programs which do a lot of work during elaboration were
difficult to build and maintain.

    Using subunits can simplify this process greatly, and were often
used that way in Ada 83.  However, as Bob Duff points out, with child
units now available in Ada 95 there is no need to use subunits this
way.  Subunits still can be used to minimize the amount of code to be
recompiled, but compilers are getting faster, and private child units
can often accomplish the same effect.
 
-- 

                                        Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...