[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return val
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form |
Date: |
Fri, 20 Jun 2014 11:46:11 +0000 |
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_19_9
Comment #5 on issue 3954 by address@hidden: Patch: Report bad return values in
user-readable form
http://code.google.com/p/lilypond/issues/detail?id=3954
Pushed to staging as
commit 7260be120168a6e0edc4472dce7f107ad4adb08f
Author: David Kastrup <address@hidden>
Date: Sun Jun 15 14:31:48 2014 +0200
Issue 3954: Report bad return values in user-readable form
An error message like
markup-def.ly:11:20: error: music function cannot return
(#<procedure line-markup (layout props args)> (Test))
is not really user-readable. At the price of some possible ambiguity,
using a LilyPond syntax form like
markup-def.ly:11:20: error: music function cannot return \markup
\line { Test}
is quite preferable.
--
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