Quantcast

The new parser and error output

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

The new parser and error output

Julien Claassen-2
Hello csound-devs and wisemen!
   I've been wondering. Since, I starting using the new parser (probbly for
about a year now), I found, that the reporting of wrong orchestra code
especially is rather cumbersome. I earnt a few lessons, like always look one
line below the reported one and things like that.
   but I was wondering, if there might already be an option for more humanly
informative otput or if work is planned for this field or if there is another
good tip to get more out of the reported errors, that will really point me
towards the actual mistakes.
   Warm regards
            Julien

=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!

======      Find my music at      ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email [hidden email] with body "unsubscribe csound"

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: The new parser and error output

Roger Kelly-2
I just installed the new 5.16 for windows.  I got an error trying pyinit.


error: syntax error, unexpected NEWLINE, expecting T_OPCODE or ',' (token "

") line 40:

>>>pyinit <<<

Parsing failed due to invalid input!

Stopping on parser failure


How to fix?




On Sun, Mar 11, 2012 at 2:17 PM, Julien Claassen <[hidden email]> wrote:
Hello csound-devs and wisemen!
 I've been wondering. Since, I starting using the new parser (probbly for about a year now), I found, that the reporting of wrong orchestra code especially is rather cumbersome. I earnt a few lessons, like always look one line below the reported one and things like that.
 but I was wondering, if there might already be an option for more humanly informative otput or if work is planned for this field or if there is another good tip to get more out of the reported errors, that will really point me towards the actual mistakes.
 Warm regards
          Julien

=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!

======      Find my music at      ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)


Send bugs reports to the Sourceforge bug tracker
          https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email [hidden email] with body "unsubscribe csound"


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: The new parser and error output

Roger Kelly-2

Resolved...just needed to clear old dlls.

On Sun, Mar 11, 2012 at 3:00 PM, Roger Kelly <[hidden email]> wrote:
I just installed the new 5.16 for windows.  I got an error trying pyinit.


error: syntax error, unexpected NEWLINE, expecting T_OPCODE or ',' (token "

") line 40:

>>>pyinit <<<

Parsing failed due to invalid input!

Stopping on parser failure


How to fix?




On Sun, Mar 11, 2012 at 2:17 PM, Julien Claassen <[hidden email]> wrote:
Hello csound-devs and wisemen!
 I've been wondering. Since, I starting using the new parser (probbly for about a year now), I found, that the reporting of wrong orchestra code especially is rather cumbersome. I earnt a few lessons, like always look one line below the reported one and things like that.
 but I was wondering, if there might already be an option for more humanly informative otput or if work is planned for this field or if there is another good tip to get more out of the reported errors, that will really point me towards the actual mistakes.
 Warm regards
          Julien

=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!

======      Find my music at      ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)


Send bugs reports to the Sourceforge bug tracker
          https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email [hidden email] with body "unsubscribe csound"



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: The new parser and error output

Julien Claassen-2
In reply to this post by Julien Claassen-2
Hello again!
   Spoken too soon. I've seen, that some errors are already reported in a more
user friendly way. So forget I said anything. :-)
   Warm regards
           Julien

=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!

======      Find my music at      ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email [hidden email] with body "unsubscribe csound"

Loading...