[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: scheme-function to provide value for \include
From:       Johan Vromans <jvromans () squirrel ! nl>
Date:       2016-06-29 14:50:04
Message-ID: 20160629165004.70449b2f () phoenix ! squirrel ! nl
[Download RAW message or body]

On Tue, 28 Jun 2016 11:05:59 +0200
David Kastrup <dak@gnu.org> wrote:

> Basically you are expecting something akin to the #include of the C
> preprocessor to accept calls of functions defined in C for specifying
> the file to include.

Except that in C #include is significantly different from the rest of
the C syntax. #-lines are all different and independent of C-lines and
syntax.

In LilyPond, \include looks like any other \keyword. And if it
looks like one, it is not unreasonable to expect it to behave similar.
See, for example, the m4 include which is a 100% ordinary m4 function.

Not that I'm going to say that %%%include would have been a better
choice ;).

-- Johan

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
[prev in list] [next in list] [prev in thread] [next in thread]