Re: [Lilypond-auto] Issue 3498 in lilypond: fatal error with toplevel-markup-identifier

[lilypond]

Comment #1 on issue 3498 by address@hidden: fatal error with  
toplevel-markup-identifier
http://code.google.com/p/lilypond/issues/detail?id=3498

This is a consequence of issue 2854 (2.17.4).  The commit message somewhat  
cryptically states

    This change just removes the STRING_IDENTIFIER
    category altogether.  Where it was used previously, MARKUP_IDENTIFIER
    is accepted now syntactically, and where the semantics indeed require
    a plain string, an error is generated explicitly in the action instead
    of leaving it to the parser to complain about bad grammar.

One case where this is relevant is string addition (which can be used
in assignments) like

    mrkp = \markup "x" + \markup "y"

so after \markup expressions there is lookahead for '+' and when this
lookahead required evaluating \mrkp itself, things go wrong.

There are similar situations for music expressions.  However, since it
is unlikely that anybody actually used string addition in LilyPond
(rather than reverting to Scheme) and it isn't documented anyway,
maybe we should just remove it.


--
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