lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Use fractions rather than Scheme pairs for \scaleDuration, timeSigna


From: dak
Subject: Re: Use fractions rather than Scheme pairs for \scaleDuration, timeSignatureFraction et al (issue 6200068)
Date: Mon, 14 May 2012 10:32:11 +0000


http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll
File lily/lexer.ll (right):

http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll#newcode487
lily/lexer.ll:487: {FRACTION}   {
On 2012/05/13 02:43:23, Keith wrote:
Stupid question, but I can't figure it out.  Can we remove this
pattern from the
rules for individual starting states, now that it is matched globally
?

Well, now I tried.

GNU LilyPond 2.15.39
Changing working directory to: `./out-test'
Processing `quantize-duration-2.ly'
Parsing...
/usr/local/tmp/lilypond/input/regression/midi/quantize-duration-2.ly:47:10:
error: syntax error, unexpected '/'
  e'''4*41
          /192 r4*7/192 d4*41/192 r4*7/192 fis,4*89/192 r4*7/192
gis4*89/192
/usr/local/tmp/lilypond/input/regression/midi/quantize-duration-2.ly:47:19:
error: syntax error, unexpected '/'
  e'''4*41/192 r4*7
                   /192 d4*41/192 r4*7/192 fis,4*89/192 r4*7/192
gis4*89/192

[...]

So the answer to this question is: no.  Maybe it has to do with the
starting state specific UNSIGNED rules firing with priority then.  I'll
try moving the FRACTION rule up, but am sceptical that this will work
out better, so just let's keep the unchanged countdown on.

http://codereview.appspot.com/6200068/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]