[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-devel
Subject:    Re: [PATCH]: Fix issue 1096
From:       Benjamin Peterson <benjamin () python ! org>
Date:       2010-05-31 0:32:11
Message-ID: loom.20100531T022908-998 () post ! gmane ! org
[Download RAW message or body]

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.






[prev in list] [next in list] [prev in thread] [next in thread]