[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3274 in lilypond: Patch: Restructure parsing o
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3274 in lilypond: Patch: Restructure parsing of reverts to avoid ambiguities in relation to BACKUP |
Date: |
Sat, 06 Apr 2013 07:18:44 +0000 |
Updates:
Status: Fixed
Labels: -Type-Enhancement -Patch-push Type-Maintainability Fixed_2_17_16
Comment #5 on issue 3274 by address@hidden: Patch: Restructure parsing of
reverts to avoid ambiguities in relation to BACKUP
http://code.google.com/p/lilypond/issues/detail?id=3274
In order to address Janek's comment terminally, pushed to staging with a
rewritten commit message as
commit eedec40e61ffd9df87060afeba71a49314877174
Author: David Kastrup <address@hidden>
Date: Thu Mar 28 18:07:22 2013 +0100
Issue 3274: Restructure parsing of reverts to avoid ambiguities in
relation
A music expression could start with BACKUP (an artificially inserted
token never present in the source code itself) due to the previous
rules. If the BACKUP mechanism is needed in different unrelated rules
applicable in similar contexts, this can lead to shift/reduce
conflicts.
While the actual (separate) code prompting this issue was rewritten in
a manner reining its BACKUP tokens in on its own and thus avoiding the
conflict triggering this issue, it still makes sense to confine the
range where BACKUP tokens are recognized to the actual limited
contexts where they are being produced, in order to keep such
conflicts down, and to stop the parser from creative reinterpretation
of situations that can only arise by programmer error.
--
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