Comment #1 on issue 1584 by [email protected]: removing parser DIGIT rule http://code.google.com/p/lilypond/issues/detail?id=1584
With regard to "magically works": that would have been my initial regtest. However, after repeating the regtest, I can corroborrate that the patch fails in the manner described by Neil.
It is not much of a surprise that it fails. What is puzzling, however, is that the unpatched Lilypond works: the same problem (namely being unable to parse 0\mm) should occur since 0 is clearly a DIGIT type token and can't be absorbed as an UNSIGNED in the rule with \mm.
Can the scanner backtrack and return UNSIGNED when DIGIT can't be absorbed? This is quite mysterious to me.
_______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
