Status: Accepted
Owner: [email protected]
CC: [email protected]
Labels: Type-Maintainability

New issue 2025 by [email protected]: Make safe utility available via new (scm safe-utility-defs) scheme module.
http://code.google.com/p/lilypond/issues/detail?id=2025

Several scm/*.scm files loaded by lily.scm use the (define-safe-public) macro. This works file when running LilyPond with Guile V1.8.*, but causes problems with Guile V2.

Using a module allows us to compile the .scm files with Guile V2.* and load the compiled files, gaining considerable benefits in performance with Guile V2.

Files affected:
scm/lily.scm
scm/chord-entry.scm
scm/chord-name.scm
scm/define-music-types.scm
scm/lily-library.scm
scm/music-functions.scm
scm/paper.scm

New file:
scm/safe-utility-defs.scm





_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to