[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4443 in lilypond: Don't pass current parser/lo
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 4443 in lilypond: Don't pass current parser/location into #{...#} call |
Date: |
Wed, 17 Jun 2015 05:29:04 +0000 |
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_19_22
Comment #4 on issue 4443 by address@hidden: Don't pass current parser/location
into #{...#} call
https://code.google.com/p/lilypond/issues/detail?id=4443
Pushed to staging as
commit 2fd5db04cdf6109e2c632337e13f29261df147b7
Author: David Kastrup <address@hidden>
Date: Fri Jun 12 09:51:40 2015 +0200
Issue 4443: Don't pass current parser/location into #{...#} call
The construct #{...#} generates a call to a function embedded-lilypond.
After issue 4422, this call passed (*parser*)/(*location*) arguments
instead of the previous parser/location arguments needed for accessing
the respective values in a different lexical environment. But since the
respective values are stored in GUILE fluids rather than in lexical
variables now, they are already passed implicitly and unnecessary as
function parameters.
--
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