Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_19_10
Comment #6 on issue 3983 by [email protected]: Patch: Avoid define-public and
define*-public with curried definitions
http://code.google.com/p/lilypond/issues/detail?id=3983
Pushed to staging as
commit 1d3beed53413315ec6c0553b003b8c5776f8c38f
Author: David Kastrup <[email protected]>
Date: Thu Jun 5 20:34:14 2014 +0200
Issue 3983: Avoid define-public and define*-public with curried
definitions
Regarding curried definitions, GUILE has problems with define-public
before version 2.0.10, and with define*-public even later.
define-safe-public is implemented by LilyPond itself rather than the
(ice-9 curried-definitions) module and is unproblematic.
This is basically a cop-out since juggling with overriding bugfix
definitions of define-public is a distraction for getting GUILEv2
migration under way that we can do without.
--
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
