New Parser: Issue with Csound Haiku IV

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

New Parser: Issue with Csound Haiku IV

Steven Yi
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: New Parser: Issue with Csound Haiku IV

Tito Latini
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: New Parser: Issue with Csound Haiku IV

Steven Yi
Fantastic, thanks!

On Sat, Jan 28, 2012 at 2:46 AM, Tito Latini <[hidden email]> 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
> [hidden email]
> 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel
Loading...