[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser togeth
From: |
lilypond |
Subject: |
Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely. |
Date: |
Wed, 21 Dec 2011 20:10:44 +0000 |
Updates:
Status: Fixed
Owner: address@hidden
Labels: -Patch-review Fixed_2_15_23
Comment #2 on issue 2131 by address@hidden: Patch: Tie LilyPond, lexer and
parser together more type-safely.
http://code.google.com/p/lilypond/issues/detail?id=2131
Well, functionally it does not really change anything. If there were a
significant problem, it should have shown as compile time errors. Since
it's ok with Patchy, I'm putting this out to staging.
The one issue that might have been possible is that %lex-param
and %parse-param have not been defined long enough in Bison. But for one
thing I can't remember not seeing them, for another we have an incestuous
pretest community: I don't think any of them will be using an older Bison.
So if that's a problem, we will be hearing from users first.
d68aac03ec19533d77a28660326fdf1c26040a5e
- Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 2011/12/21
- Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 2011/12/21
- Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely.,
lilypond <=
- Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 2011/12/21
- Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 2011/12/31