[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Variables and Bookpart
From: |
Jean Abou Samra |
Subject: |
Re: Variables and Bookpart |
Date: |
Mon, 13 Mar 2023 00:45:38 +0100 |
User-agent: |
Evolution 3.46.4 (3.46.4-1.fc37) |
Le dimanche 12 mars 2023 à 16:34 -0700, Saul Tobin a écrit :
A slightly nicer syntax to workaround this limitation is to use the function:
parserDefine =
#(define-void-function (name val)(symbol? scheme?)
(ly:parser-define! name val))
Then instead of var = { ... } you can write \parserDefine var { ... }.
I believe this was posted on the list a few years ago.
Yes. However, if you end up finding this useful, I consider it likely that it indicates you should refactor your code. Off the top, I can't even think of a case where this is the best way to proceed.
signature.asc
Description: This is a digitally signed message part
- Variables and Bookpart, Mark Stephen Mrotek, 2023/03/12
- Re: Variables and Bookpart, Jean Abou Samra, 2023/03/12
- RE: Variables and Bookpart, Mark Stephen Mrotek, 2023/03/12
- Re: Variables and Bookpart, Hans Aikema, 2023/03/12
- Re: Variables and Bookpart, Valentin Petzel, 2023/03/12
- Re: Variables and Bookpart, Saul Tobin, 2023/03/12
- Re: Variables and Bookpart,
Jean Abou Samra <=
- Re: Variables and Bookpart, Saul Tobin, 2023/03/12
- Re: Variables and Bookpart, Jean Abou Samra, 2023/03/12
- Re: Variables and Bookpart, Saul Tobin, 2023/03/12
- Re: Variables and Bookpart, Jean Abou Samra, 2023/03/12
- RE: Variables and Bookpart, Mark Stephen Mrotek, 2023/03/12
- RE: Variables and Bookpart, Mark Stephen Mrotek, 2023/03/12
- Re: Variables and Bookpart, Jean Abou Samra, 2023/03/12
- RE: Variables and Bookpart, Mark Stephen Mrotek, 2023/03/12
- Re: Variables and Bookpart, Werner LEMBERG, 2023/03/13