I think the output needs to be a level past your program. For example, it needs to answer the question, "what is the next item to display?" with "a middle C# quarter note that starts a tie with the chord A#dim over it and a staccato dot over it." or "a double bar line that repeats on the left that ends a first ending marking."
This project is ridiculously esoteric as some conceive of it. All that's required is a translation of the (strange!) notation which abc is.
A header and a list of musical objects is all that's required: composer, notes, clefs, chord names, barline, maybe line breaks... whatever.
Then it's up to each application to do as its writer wishes with the information: the only important thing is not to throw any information away which the original abc file had. And it seems clear to me that "what shall I display next?" is not the place of a parser! The calling programs might not all want the same display order, or might want to ignore some of the data!
-- Bernard Hill Braeburn Software Author of Music Publisher system Music Software written by musicians for musicians http://www.braeburn.co.uk Selkirk, Scotland
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
