Am Samstag, 29. Mai 2010, um 17:04:34 schrieb Benjamin Peterson: > 2010/5/28 Reinhold Kainhofer <reinh...@kainhofer.com> schrieb: > > Am Donnerstag, 27. Mai 2010, um 15:39:46 schrieb Carl Sorensen: > >> Benjamin Peterson prepared a patch to fix this issue. > >> > >> It's in the lexer, and I'm not at all comfortable with the lexer. > >> However, the patch has been demonstrated to work and to not break the > >> regtests. > > > > Actually, while it does not break any current regtests, it does not work > > in all cases. > > Thank you for your extensive tests. Before addressing the problems, > though, I was wondering what your use-case for ly:parser-parser-file > is. Is it to include a programmatically created string into the > current file as if with an \include?
Yes, the two cases where we encountered a problem with ly:parser-parse-string were: -) Including files just once. I.e. if a file had already been included, don't include it a second time -) Conditionally including a user-specified init file: in ly/init.ly do something similar to \include, but use the file name specified in a command line option. This has to be done in scheme, since scheme is needed to evaluate the command-line arguments. > 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 :( Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
