[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH]: Fix issue 1096
From: |
Benjamin Peterson |
Subject: |
Re: [PATCH]: Fix issue 1096 |
Date: |
Mon, 31 May 2010 00:32:11 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Reinhold Kainhofer <reinhold <at> kainhofer.com> schrieb:
> > If so, I think a new interface,
> > that would simply insert the string into the current stream would make
> > more sense.
>
> Yes, you are probably right. However, I don't know enough of the parser
> internals to implement this myself :(
I've attached a new patch to the issue. It adds a new function,
ly:parser-include-string. This appends the string passed to it right after the
scheme expression the calls appears in. It works like this:
#(ly:parser-include-string parser "{ a b c d }")
As for ly:parser-parse-string and ly:parser-parse-file, I think they should
probably be banned in ly files, since they seem to only cause trouble.
- Re: [PATCH]: Fix issue 1096, (continued)
- Re: [PATCH]: Fix issue 1096, David Kastrup, 2010/05/27
- Re: [PATCH]: Fix issue 1096, Carl Sorensen, 2010/05/27
- Re: [PATCH]: Fix issue 1096, Graham Percival, 2010/05/27
- Re: [PATCH]: Fix issue 1096, Carl Sorensen, 2010/05/27
- Re: [PATCH]: Fix issue 1096, Benjamin Peterson, 2010/05/27
- Re: [PATCH]: Fix issue 1096, Carl Sorensen, 2010/05/27
- Re: [PATCH]: Fix issue 1096, David Kastrup, 2010/05/28
Re: [PATCH]: Fix issue 1096, Reinhold Kainhofer, 2010/05/27
Message not available
Re: [PATCH]: Fix issue 1096, Reinhold Kainhofer, 2010/05/29