Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(626)

Issue 109360043: Avoid define-public and define*-public with curried definitions (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
9 years, 10 months ago by dak
Modified:
9 years, 6 months ago
Reviewers:
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

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.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+49 lines, -25 lines) Patch
M scm/chord-name.scm View 2 chunks +2 lines, -1 line 0 comments Download
M scm/flag-styles.scm View 1 chunk +2 lines, -1 line 0 comments Download
M scm/music-functions.scm View 7 chunks +12 lines, -6 lines 0 comments Download
M scm/output-lib.scm View 7 chunks +16 lines, -8 lines 0 comments Download
M scm/tablature.scm View 1 chunk +2 lines, -1 line 0 comments Download
M scm/titling.scm View 3 chunks +4 lines, -2 lines 0 comments Download
M scm/translation-functions.scm View 4 chunks +10 lines, -5 lines 0 comments Download
M scripts/musicxml2ly.py View 1 chunk +1 line, -1 line 0 comments Download

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b