| Congratulations Steven!
You are doing great work on getting the UDOs and if/thens, etc. working for
the new parser! Your tech guide to the orchestra parser is very useful too.
I have been looking in that region myself recently because of the line count
issues.
A few comments:
Your tech guide asks whether the orch preprocessing happens in the lexer or
parser stage. You may have since figured this out, but it all occurs in
rdorch.c (rdorchfile) and it seems to trump nearly all other syntax
structures.
I am thinking that one possible solution for correct error line numbers with
the new parser would be to add a line count member to every node in the AST
(and it may be necessary to associate line numbers with every lexer token as
well). The reason is that individual arguments to an opcode may be on
different "physical" lines (or even files?) when using line continuations.
Finally, I am wondering what your thoughts on dead code elimination are? It
seems that some opcodes produce side effects other than their outputs (and
some change their inputs!). I wonder if this makes dead code identification
more difficult?
Thanks for all the work!
Anthony
Steven Yi wrote on 12/12/07 3:08 AM:
> I'm very happy to report that after a couple hours of debugging I
> found out what was wrong with the UDO parsing/compiling with the new
> parser and the new parser is now able to parse/compile/run with UDO's!
> This was one of the biggest language features left which I had on my
> list.
> I have attached a PDF version of a technical document I have been
> writing as I have been working on the parser.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |