Rubbish. To be useful, the parser should be a procedure with an API which can be called from a standard executable program. If you produce an acsii file, you have just replaced one problem with another.
----- Original Message ----- From: "Bernard Hill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 25 April 2004 13:29 Subject: Re: [abcusers] !Current specification! > In message <[EMAIL PROTECTED]>, Stephen Kellett > <[EMAIL PROTECTED]> writes > >C++ Surely? C is very restrictive in comparison. Writing object based > >code in C is hard work (read: un-necessary extra code, and lack of type > >safety) compared to C++. > > > >Java and C# are not worthwhile alternatives. Both quite restrictive > >because nothing is truly passed as a reference (try modifying a string > >object you pass in and see if it really was changed after the method > >call - if it was really passed as a reference it would be). Makes > >things trivial in C and C++ a real pain in Java and C#. > > > >Stephen > > In my opinion any parser should produce ascii code and be > self-contained, written as a command-line procedure using stdin and > stdout > > abcparse <inputfilename >outputfilename > > > The structure of the outputfile would probably obey some sort of XML > language (although I hate it). > > -- > 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 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
