If the parser were being written in lockstep with the specification, proper design might indeed be the result. Kindof an evolution meets extreme programming approach. (Not that I really ever understood Extreme programming).
Would anyone else be interested in such?
Neil Jennings wrote:
The draft standard seems to contain many things which make life difficult for parsers. A bit of proper design could have avoided this. I shoud throw my parser away and start again - but it would take some time! There is so much else to write without having to waste time reinventing wheels.
----- Original Message ----- From: "Christian M. Cepel" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 23 April 2004 15:32 Subject: Re: [abcusers] !Current specification!
http://www.tullochgorm.com/lists.htmlI was thinking about this last night...and I don't see a problem with parsing for a *x* token, a !x! token and ! at the end of a line, even if there are whitespace characters between ! and your EOL token. A backwards compatible, or version insensitive parser, which would be the kindest to your end user who may have grabbed a tune off the net, and not even have looked at the abc, or know even how to edit the abc, would be the best option.... not insensitive about all things, but kind enough to recognize that !x! is valid 1.7.6 stuff and display it. You could even make your software encourage use of the newer constructs. "Your tune contains outdated notation that can easily be brought up to date w/o changing the way it displays or sounds when played. Would you like to update the notation? Y/N" A bit Microsoft word-esk, but even so.
Would this not be so?
Btw, abcmusicnotation.org and abcnotation.org should be well on their way, propagating through dns servers and available to most.
David Webber wrote:
From: "Neil Jennings" <[EMAIL PROTECTED]>
In 2.0, there is a %% directive in which the version is specified. I would expect that this would be mandatory if the file is written using 2.0 standard or later, otherwise there wouldn't be much point in having it.
Ok that helps. But it still seems pretty silly making a new official standard (1.7.6) with !pp! while the draft 2.0 standard deprecates it in favour of using ! for something else and using +pp+.
Dave David Webber Author MOZART the music processor for Windows - http://www.mozart.co.uk For discussion/support see http://www.mozart.co.uk/mzusers/mailinglist.htm
To subscribe/unsubscribe, point your browser to:
http://www.tullochgorm.com/lists.html--
//Christian
Christian Marcus Cepel | And the wrens have returned & [EMAIL PROTECTED] icq:12384980 | are nesting; In the hollow of 371 Crown Point, Columbia, MO | that oak where his heart once 65203-2202 573.999.2370 | had been; And he lifts up his Computer Support Specialist, Sr. | arms in a blessing; For being University of Missouri - Columbia | born again. --Rich Mullins
To subscribe/unsubscribe, point your browser to:
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
--
//Christian
Christian Marcus Cepel | And the wrens have returned & [EMAIL PROTECTED] icq:12384980 | are nesting; In the hollow of 371 Crown Point, Columbia, MO | that oak where his heart once 65203-2202 573.999.2370 | had been; And he lifts up his Computer Support Specialist, Sr. | arms in a blessing; For being University of Missouri - Columbia | born again. --Rich Mullins
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
