Re: Changing @Use semantic

[Jeff Kingston]

Uwe proposes allowing @Use within inner scopes as well as at the
outer level.  This might be reasonable but it seems to be addressing
a different problem.

The observation that the @Include of a package is logically coupled
with its @Use - you include it and customize it as you go - makes
a lot of sense.  It's like object-oriented programming really, like
the creation of a (say) diagram-printing object from a @DiagramPrint
class.  But again, I don't think it solves the problem.  Suppose you
could indeed write

    @IncludeAndUse { @DiagramPrint ... }

how would that help to reduce the number of setup files?

Jeff


Incidentally, recent versions of Lout allow parameters to be given
and import clause.  This may be relevant to Uwe's needs for a local
@Use.