|
From: | lilypond |
Subject: | Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel |
Date: | Tue, 17 Aug 2010 15:40:56 +0000 |
Comment #20 on issue 1096 by n.puttock: ly:parser-parse-string segfaults when directly called at toplevel
http://code.google.com/p/lilypond/issues/detail?id=1096+ parser->parser_error("ly:parser-parse-string only valid with new parser");
I think a message gently pointing the user in the direction of ly:parser-include-string would be preferable. Even with a cloned parser, ly:parser-parse-string doesn't work properly within a .ly file.
[Prev in Thread] | Current Thread | [Next in Thread] |