Re: Where can you put def ines?

[Valeriy E. Ushakov]

On Tue, Aug 17, 1999 at 11:06:07AM +0100, Mark Summerfield wrote:

> I want to do something like this:
> 
> def @Scene left x right y {
>     @Section
>       @Title { x }
>     @Begin
>     @Include { y }
>     @End @Section
> }
> 
> Example of use:
> 
> { The One Where Def Actually Works } @Scene { def.lt }

@Include is "immediate".  What's wrong with 

    import @BasicSetup @DocumentSetup @ReportSetup
    def @Scene left x right y { @Section @Title { x } { y } }

    { The One Where Def Actually Works } @Scene { @Include { def.lt } }

Or even better, put the title and related stuff into the included file
directly and just @Include it - this way you keep all the pertinent
information in one place.

OTOH, the "deferred" variant of @Include should be simple to add, and
in fact you can emulate it with (admittedly ugly):

    # warning: no implicit .lt is added
    def @Filter { cat `cat @FilterIn` > @FilterOut }

I'm just not sure if deferred @Include is very useful.  Explicit
@Include done by the caller is self-documenting and easier to read.
If you need something more that just including one file - chances are
that you will need more sophisiticated processing anyway and will use
@Filter.

SY, Uwe
-- 
address@hidden                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen