[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: \include inside function
From: |
David Kastrup |
Subject: |
Re: \include inside function |
Date: |
Tue, 01 Feb 2022 21:33:59 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Valentin Petzel <valentin@petzel.at> writes:
>> And it still breaks down because at the top level, LilyPond input does
>> not reflect a static structure but directs actions, actions that have
>> immediate consequences _while_ still reading ahead.
>
> I do not understand why this matters here? Doesn’t this only matter
> while we are parsing the file?
You won't get far without parsing the file.
> I understand that delayed scheme calls to variables defined in the
> subfile poses some challenge, but such things should be rather
> uncommon.
Feel free to create an implementation. That will apparently be easier
than to prove viability to me.
--
David Kastrup
- Re: \include inside function, (continued)
- Re: \include inside function, David Kastrup, 2022/02/01
- Re: \include inside function, Valentin Petzel, 2022/02/01
- Re: \include inside function, David Kastrup, 2022/02/01
- Re: \include inside function, Valentin Petzel, 2022/02/01
- Re: \include inside function, David Kastrup, 2022/02/01
- Re: \include inside function, Valentin Petzel, 2022/02/01
- Re: \include inside function, David Kastrup, 2022/02/01
- Re: \include inside function, Valentin Petzel, 2022/02/01
- Re: \include inside function, David Kastrup, 2022/02/01
- Re: \include inside function, Valentin Petzel, 2022/02/01
- Re: \include inside function,
David Kastrup <=
- Re: \include inside function, Valentin Petzel, 2022/02/01
- Re: \include inside function, Jean Abou Samra, 2022/02/01
- Re: \include inside function, Jean Abou Samra, 2022/02/01
- Re: \include inside function, Valentin Petzel, 2022/02/01
Re: \include inside function, David Wright, 2022/02/01
Re: \include inside function, Valentin Petzel, 2022/02/01