]> git.donarmstrong.com Git - lilypond.git/commit
projects / lilypond.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6cce037) | patch
Issue 3954: Report bad return values in user-readable form
authorDavid Kastrup <dak@gnu.org>
Sun, 15 Jun 2014 12:31:48 +0000 (14:31 +0200)
committerDavid Kastrup <dak@gnu.org>
Fri, 20 Jun 2014 11:43:26 +0000 (13:43 +0200)
commit7260be120168a6e0edc4472dce7f107ad4adb08f
treef0bfdf3df112e46ad64c1bd793b5c7556fcd73cbtree | snapshot
parent6cce037bef16ba87a3531482d89152a52dbfa952commit | diff
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.
scm/ly-syntax-constructors.scm diff | blob | history
Debian packaging of lilypond