(Sorry, that should have read "Google Closure Compiler" not "Google
Compiler".)
Just to clarify my question, does the following snippet produce the *new*
AST or the *old* AST?
Context cx = Context.enter();
cx.setLanguageVersion(Context.VERSION_1_5);
CompilerEnvirons compEnv = new CompilerEnvirons();
compEnv.initFromContext(cx);
Parser parser = new Parser(compEnv, errorReporter);
AstRoot root = null;
try {
root = parser.parse(jsSource, jsFilename, 1);
} catch (EvaluatorException ex) {
// ...
} finally {
Context.exit();
}
If it is the old AST, what is the entry point to generating the new AST?
Thanks,
smm
On Wed, Nov 3, 2010 at 10:03, Stephen McKamey
<[email protected]<stephen%[email protected]>
> wrote:
> I'm curious what is the current state of the new AST API rumored for 1.7R3?
> I have a copy of the CVS head. Is this sufficient to build a walkable AST
> with the new API? Anyone have a pointer on how to best do this? I believe
> Google Compiler does this with a fork of the Rhino code.
>
> The last post I can find about this is a year or more old.
>
> Thanks in advance,
> smm
>
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
