Closed
Bug 583592
Opened 14 years ago
Closed 14 years ago
Narcissus ?: parsing problem
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: brendan, Unassigned)
References
()
Details
See URL. Shu, can you take this bug? Thanks, /be
Comment 1•14 years ago
|
||
This is fixed in TM tip. I can't seem to assign or close this bug though.
Comment 2•14 years ago
|
||
Sorry if this is well known, but may I ask you what do you mean by TM tip? Tracemonkey tip? Thanks.
Comment 3•14 years ago
|
||
Yes, exactly.
Comment 4•14 years ago
|
||
And where can I find it? Is it a branch or fork or... Thx.
Comment 5•14 years ago
|
||
You can do:
> hg clone http://hg.mozilla.org/tracemonkey/
Narcissus is to be found in tracemonkey/js/narcissus
Comment 6•14 years ago
|
||
http://hg.mozilla.org/tracemonkey/rev/1c7d7b849b21
Whiteboard: fixed-in-tracemonkey
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•14 years ago
|
Whiteboard: fixed-in-tracemonkey
Comment 8•14 years ago
|
||
Tracemonkey is the JavaScript development branch. It is merged into mozilla-central on a regular basis.
Comment 9•14 years ago
|
||
Wow, pretty huge rewrite. Basically means that I will redo my port to Python under: http://github.com/unify/jstools May I ask you whether you plan further major changes to the parser?
Comment 10•14 years ago
|
||
Sebastian, Shu is working on an SSA analysis for Narcissus. The parser refactoring is mostly done. We will add another building (SSABuilder), but most of the existing code should be stable now.
Reporter | ||
Comment 11•14 years ago
|
||
This bug is fixed, but it is certainly not a dup of bug 579230 "Builder pattern refactor of the narcissus parser." It's a dependent bug, s'all. /be
Reporter | ||
Comment 12•14 years ago
|
||
Fixed by Shu's recursive descent rewrite for bug 579230. /be
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 13•14 years ago
|
||
Sebastian, thanks for tweeting about the old ?: bug. Regarding future changes, as Andreas notes the recursive descent parser is pretty stable for the language that it parses -- it is based on SpiderMonkey's parser. However there are more changes to look out for in the future, which will be based on the http://wiki.ecmascript.org/doku.php?id=harmony:proposals and http://wiki.ecmascript.org/doku.php?id=strawman:strawman proposals. /be
You need to log in
before you can comment on or make changes to this bug.
Description
•