Comment #7 on issue 4472 by [email protected]: Let \mark and Mark_engraver act
consistently
https://code.google.com/p/lilypond/issues/detail?id=4472
It's not a good idea to have the boundaries of a function call depend on
material not even _in_ the function call. Since the function call may
itself be an argument of a function call, arbitrary material may follow
next. How to decide which function call it belongs to?
It's better not to rely on lookahead here. There are a few situations
involving single-token lookahead but not for the sake of checking an
optional argument. For example:
{ \displayLilyMusic c c }
Here the second c is tokenized before LilyPond can decide that a token of
this kind cannot belong to the music expression following \displayLilyMusic
(whereas a 4 would become part of the expression). But that's not the
parsing of a full expression and checking against a predicate: it's just
the single-token lookahead the LALR(1) parser can deal with.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
