[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4422 in lilypond: Obsolete parser/location arg
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 4422 in lilypond: Obsolete parser/location arguments to music functions |
Date: |
Wed, 03 Jun 2015 09:00:23 +0000 |
Comment #8 on issue 4422 by address@hidden: Obsolete parser/location arguments
to music functions
https://code.google.com/p/lilypond/issues/detail?id=4422
Oh great. Staging-patchy told me off. I, uh, had added some trivial
further corrections before pushing. So I took a look at the error message
and had a forehead-slap. I fixed this problem (music function calls
already transfer location to 'origin, so it was just a matter of removing
the unnecessary additional insertion of the no longer available "location"
variable) and pushed again. Let's hope I did not have more easter eggs.
commit 2f9328a294a9317af7fe91ebdb00534e0cba29ea
Author: David Kastrup <address@hidden>
Date: Wed May 27 17:05:34 2015 +0200
Issue 4422/7: Documentation fixes and Changelog
commit ade3215602fec71d7a700f5093e1e4e75371c7f2
Author: David Kastrup <address@hidden>
Date: Sun May 31 20:37:14 2015 +0200
Issue 4422/6: Fix (define-music-function (parser ... uses in scm/
commit 98ac53591234404cd70c5eebd370a598ec74095b
Author: David Kastrup <address@hidden>
Date: Wed May 27 04:25:32 2015 +0200
Issue 4422/5: Run scripts/auxiliar/update-with-convert-ly.sh
commit 0200dabbc6e9bfa91c38f1199a2cdf9bfb43d026
Author: David Kastrup <address@hidden>
Date: Wed May 27 03:00:16 2015 +0200
Issue 4422/4: convert-ly rule for removing parser/location
commit c2539ac9d11b835d3b4560f60a36060f6e0a23d4
Author: David Kastrup <address@hidden>
Date: Wed May 27 01:35:08 2015 +0200
Issue 4422/3: Remove parser/location args from music function calls
When a music function definition starts with a parameter named "parser",
a compatibility definition is created that recreates the parameters
from the fluid accessors (*parser*) and (*location*) when necessary.
commit 11990933427a4a166764ca800d54387523ac0355
Author: David Kastrup <address@hidden>
Date: Wed May 27 01:01:38 2015 +0200
Issue 4422/2: Fix various jumbled parser/location argument pairs
commit 9a6b086e5af718384faa1395dcb1ea657724e616
Author: David Kastrup <address@hidden>
Date: Tue May 26 13:36:53 2015 +0200
Issue 4422/1: Remove parser/location global variable setup
Instead of relying on the global parser/location work horse (or
respective symbols in local scope), now fluids %parser/%location and
getter functions (*parser*)/(*location*) are employed for setting up the
general parsing and providing #{...#} with accurate information.
This patch removes the global setup and internal information flow: there
is still a variable "parser" being set in local parser modules.
--
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