"Aaron M. Renn" <[EMAIL PROTECTED]> writes:
>
> As you can see, a lot of this is parallelalizable. Per usual I was thinking
> of something more ambitious. To the best of my knowledge there is no
> standard parsing API. I was thinking that there should be a "parselet" API
> for applications that need to parse Java source files (JavaDeps, JavaDoc,
> etc). This should make it fairly easy to write programs that operate on
> Java source without having muck around with your own parser engine. But
> that concept was as far as I got.
I have something almost exactly like this as a part of the compiler I
am writing. You can write AST walkers that traverse the parse tree
after name resolution and type checking are done and collect
information and/or modify the parse tree. I have a 100 line
dependency generator, but the compiler is not 100% functional
currently so its not yet ready to replace JavaDeps.
I am currently working with Paul to try to set things up so other
people can contribute. More info soon...
--
Geoff Berry
