bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond


From: lilypond
Subject: Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond
Date: Sat, 03 Dec 2011 21:43:00 +0000


Comment #1 on issue 2072 by address@hidden: Add proper complex variables to Lilypond
http://code.google.com/p/lilypond/issues/detail?id=2072

Well, I have to take back that particular syntax since it could not be made to work: detecting assignment would require seeing the = as a lookahead token, and once we see a different lookahead token, it is too late to inject an expression token into the input stream since the parser has already made decisions based on the lookahead token. So one would have to use something like
\put \violin1 { ... }
for assignment and \violin1 for accessing it, or
\violin1 = { ... }
for assignment and \get\violin1 for accessing it. Either case, the decision between assignment and use can be made without looka raising its ugly head.

It may be possible to use the somewhat more natural syntax \set \violin1 { ... } as well, but that would add another unrelated meaning to \set.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]