lilypond-auto
[Top][All Lists]
Advanced

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

[Lilypond-auto] Issue 3983 in lilypond: Patch: Avoid define-public and d


From: lilypond
Subject: [Lilypond-auto] Issue 3983 in lilypond: Patch: Avoid define-public and define*-public with curried definitions
Date: Tue, 01 Jul 2014 14:43:55 +0000

Status: Started
Owner: address@hidden
Labels: Type-Enhancement Patch-new

New issue 3983 by address@hidden: Patch: Avoid define-public and define*-public with curried definitions
http://code.google.com/p/lilypond/issues/detail?id=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.

http://codereview.appspot.com/109360043

--
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



reply via email to

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