Hi!
On Fri, 12 Feb 1999 Geoff Berry wrote:
>"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.
Just a few questions:
Is your parser 100% PD? (I'd need it for a OSS UML project).
You think, that there's a chance to parse C++ with the same API? (Not the same
parser, of course.)
I work on a UML tool and my task is to do the source parsing. I use JavaCC
with modified example grammars at this time, but there's a problem with the
grammar distribution, and so I'm looking for an alternative.
TIA,
Andreas
