|Subject:||Re: LilyPond 2.5.31 released|
|Date:||Tue, 14 Jun 2005 22:55:13 -0700|
On Jun 14, 2005, at 5:54 PM, Han-Wen Nienhuys wrote:
Unfortunately, you also added a tiny bit of breakage in the MacOS X version: In framework-ps.scm, when calling fondu, you replaced the call to system (which returns a numeric status) with a call to ly:system (which throws an exception or returns nothing). As a result, every successful call to fondu blows up with a message like:
Layout output to `tunisia.ps'...(/Library/Fonts/Verdana Verdana)/sw/share/lilypond/2.5.31/scm/lily-library.scm:338:8: In procedure = in _expression_ (= lst r):
/sw/share/lilypond/2.5.31/scm/lily-library.scm:338:8: Wrong type argument in position 1: #<unspecified>
One way to fix this is to add a status return to ly:system:
--- /sw/build/lilypond-devel-2.5.31-1/lilypond-2.5.31/scm/backend-library.scm 2005-06-14 12:45:16.000000000 -0700
+++ /sw/share/lilypond/2.5.31/scm/backend-library.scm 2005-06-14 22:44:57.000000000 -0700
@@ -24,7 +24,8 @@
(ly:message (_ "`~a' failed (~a)") command status)
;; hmmm. what's the best failure option?
- (throw 'ly-file-failed)))))
+ (throw 'ly-file-failed))
(define-public (sanitize-command-option str)
Presumably, you'd prefer to instead replace the numeric status check in framework-ps.scm with a catch, but I'll leave that up to you to ponder.
With the above fix, I can confirm that my test succeeded on MacOS X.
|[Prev in Thread]||Current Thread||[Next in Thread]|