Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %pure-parser instead of %pure_parser

[lilypond]

Updates:
        Summary: Patch: lily/parser.yy: Use %pure-parser instead of %pure_parser
        Status: Fixed
        Labels: -Type-Enhancement -Patch-push Type-Maintainability Fixed_2_17_24

Comment #12 on issue 3488 by address@hidden: Patch: lily/parser.yy:  
Use %pure-parser instead of %pure_parser
http://code.google.com/p/lilypond/issues/detail?id=3488

Pushed to staging as
commit 2848a5e030f2fe38e4184e25c6b7df5aaad6489d
Author: David Kastrup <address@hidden>
Date:   Mon Aug 5 14:19:06 2013 +0200

    Issue 3488: lily/parser.yy: Use %pure-parser instead of %pure_parser

    While %pure-parser is already deprecated for Bison 3.0, it is still
    supported as opposed to %pure_parser which has been removed altogether
    in Bison 3.0.  The currently recommended form %define api.pure has
    only become available with Bison 2.3b, and there are currently older
    versions of Bison in use with LilyPond.  So the followup move of
    replacing the already deprecated %pure-parser with %define api.pure is
    left for a later point of time.


Silly as it is, the one-line change to %define api.pure will be left for a  
later time.

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