> You might have to import a lot more than only the parser, just to make
> machinery such as identifiers work. It might be easier to just paste
> the relevant parts of the parser into a separate .y file.
>
I was thinking that I might use the exact same objects as lilypond.
Keep intact the notions of spanner, request, and all that. Everything
that has to do with how the music sounds would stay in. Basically, I
want to render music into a Python based compositional environment
instead of to paper (or a MIDI file) using Mudela. The advantages are
that Mudela would be a common link between my tool and Lilypond so I
would only need to know one language (plus I couldn't design a better
Sounds reasonable. I am curious how difficult linking Python would
be. The bad news is, that there is only a little amount of documentation.
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
