[Webkit-unassigned] [Bug 34019] Custom-written JavaScript parser

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=34019





--- Comment #35 from Zoltan Herczeg <zherczeg at webkit.org>  2010-02-03 07:04:13 PST ---
Oliver, what is your opinion about the syntax checker patch?

Tasks ahead:

* I havent't broken the node generator mechanism, yet. Partial object
generation would only be helpful for few, complex nodes, like try, switch, for
(and they need to do some consistency check before emitByteCode).
Unfortunately, we still have to store the parsing status, which means perhaps
we can decrease the required number of stack items to 2 down from 3.

* line info, and divot points. It is a mess now, every node do the things
differently (depending on how the bison parsing them). We should introduce
clear rules and follow them. We can do that now using our predictive parser.

* generating parser rules. I have no idea how to do this, since we have so many
different language constructions. I couldn't find any real node grouping rules.
The two major groups are expressions and statements. Statements are more
difficult to implement than expressions.

Is there anything else?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.