Re: Function Calls by Address

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

Marin David Condic wrote:
 
> I think that the use of child units contributes a lot to better overall
> code. If nothing else, it helps with configuration management and change
> control issues by better isolating where changes occur.
> 
> I never liked the "is separate" and I'm not sure I could tell you why. I
> wasn't fond of inheriting such a large context which was not immediately
> visible in the code I was editing. I didn't like the fact that recompiling
> the parent package would cause recompilation of all the separate units
> because you effectively hit their specs...
 
    But that is looking at things upside down.  One of the most powerful
uses of subunits that a subunit can have a context clause.  This allows
you to migrate some or all of the context clauses from the library unit
or body down to the subunits.  Now recompiling that package spec will
only result in needing to recompile some of the subunits, not the
library unit body and all the subunits.

    But it is the semantic view of this, ignoring recompilation times
that makes subunits so powerful.  Instead of one monolithic body with
dozens of with clauses, you have a body and subunits with only a few
withs on each.

    Finally you can use subunits to write programs that cannot be easily
written without them.  The easiest way to see this is to imagine trying
to write a tool to remove subunits from a program.  It cannot be done
textually, and even with ASIS it would be a very difficult problem.
-- 

                                        Robert I. Eachus

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