extension point for new compiler warnings? [message #122012] |
Tue, 25 November 2003 19:08  |
Eclipse User |
|
|
|
Originally posted by: tcube2002.yahoo.com
I have a plugin that listens for ElementChangedEvents, generates an AST for the containing
file and generates warnings based on a our own custom source checks (essentially emulating
our own additional compiler warnings). The problem is that it's pretty expensive to
AST.parseCompilationUnit(..), and considering the compiler just ran moments before to
incrementally compile the same file (and probably did the exact same thing), it seems
wasteful. Is there any way to either hook into the compiler's AST as it's working via a
compiler extension point, or is there some more efficient way to get an AST that may have
recently been generated by someone else for the same ICompilationUnit?
Thanks
Mike Schrag
|
|
|
Re: extension point for new compiler warnings? [message #122228 is a reply to message #122012] |
Wed, 26 November 2003 05:30  |
Eclipse User |
|
|
|
Note if you're not in autobuild mode, the compiler would not have run.
However you can still enter a feature request asking to share ASTs.
Jerome
"Mike Schrag" <tcube2002@yahoo.com> wrote in message
news:bq0qpj$ohv$1@eclipse.org...
> I have a plugin that listens for ElementChangedEvents, generates an AST
for the containing
> file and generates warnings based on a our own custom source checks
(essentially emulating
> our own additional compiler warnings). The problem is that it's pretty
expensive to
> AST.parseCompilationUnit(..), and considering the compiler just ran
moments before to
> incrementally compile the same file (and probably did the exact same
thing), it seems
> wasteful. Is there any way to either hook into the compiler's AST as it's
working via a
> compiler extension point, or is there some more efficient way to get an
AST that may have
> recently been generated by someone else for the same ICompilationUnit?
>
> Thanks
> Mike Schrag
>
|
|
|
Powered by
FUDForum. Page generated in 0.03231 seconds