[Cs-dev] New Parser: Issue with Csound Haiku IV

Date	2012-01-27 22:48
From	Steven Yi
Subject	[Cs-dev] New Parser: Issue with Csound Haiku IV
	Hi All, Just reporting an issue that I'm seeing. With Iain McCurdy's Csound Haiku IV from : http://iainmccurdy.org/csoundhaiku.html The parser reports a problem with this instrument: instr reverb aL, aR reverbsc gasendL, gasendR, 0.9, 10000 outs aL, aR clear gasendL, gasendR endin error: syntax error, unexpected T_OPCODE, expecting T_IDENT or INTEGER_TOKEN or '+' (token "reverb") line 70: >>> instr reverb <<< I'm thinking this is a lexer issue, that the lexer is returning an opcode and not a string. Possible solution I can think of is to accept either string or opcode in the parser and just read it as a string if opcode. Note: this works with the old parser, so should be supported. Thoughts? steven ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2012-01-28 07:46
From	Tito Latini
Subject	Re: [Cs-dev] New Parser: Issue with Csound Haiku IV
Attachments	None

Date	2012-01-28 15:21
From	Steven Yi
Subject	Re: [Cs-dev] New Parser: Issue with Csound Haiku IV
	Fantastic, thanks! On Sat, Jan 28, 2012 at 2:46 AM, Tito Latini wrote: > Now it's possible > > instr reverb, if, db, 6, then, do, +jitter, gauss, od > > On Fri, Jan 27, 2012 at 05:48:09PM -0500, Steven Yi wrote: >> Hi All, >> >> Just reporting an issue that I'm seeing. With Iain McCurdy's Csound >> Haiku IV from : >> >> http://iainmccurdy.org/csoundhaiku.html >> >> The parser reports a problem with this instrument: >> >> instr reverb >> aL, aR reverbsc gasendL, gasendR, 0.9, 10000 >> outs aL, aR >> clear gasendL, gasendR >> endin >> >> error: syntax error, unexpected T_OPCODE, expecting T_IDENT or >> INTEGER_TOKEN or '+' (token "reverb") line 70: >> >>> instr reverb <<< >> >> >> I'm thinking this is a lexer issue, that the lexer is returning an >> opcode and not a string. Possible solution I can think of is to >> accept either string or opcode in the parser and just read it as a >> string if opcode. Note: this works with the old parser, so should be >> supported. Thoughts? >> >> steven > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net