On Mar 13, 2:17 pm, Glenn Boysko <[EMAIL PROTECTED]> wrote: > Hello: > > I've been using Rhino for some time as a parser for JavaScript. The > lack of a complete grammar for ANTLR makes Rhino a good option for me. > I'm using it for things like specialized documentation tools (JavaDoc- > style docs for JavaScript classes) or other code analysis. > > I'm sure that you get a lot of these types of questions. What do you > recommend? > > For example, I've been using 1.5 and 1.6 in the past and found no node > visitor class. Does one exist in 1.7? There doesn't seem to be a way > to search for a node (by type) in 1.6 either. > > If you have any suggestions for writing JavaScript parsers based on > Rhino, I'd really appreciate it. > > Thanks, > Glenn
Rhino 1.7 doesn't have any more support for what you want than 1.5 or 1.6. It is possible to write code that traverses over the intermediate representation. See NodeTransformer.java for an example. This is a commonly-requested feature, however, and we're looking hard at implementing more rational and easy-to-use abstract syntax trees for 1.7R2. --N _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
