Re: [Dltk-dev] Support more that one ISourceParser

[Andrei Sobolev <andrei.sobolev@xxxxxxxxx>]

Hi Edgar,

As I understand you use antlr runtime to make AST, build model, etc. Is
it correct?

You want to have different ISourceParser's for different projects? Or
for different files?

If you want to have parser for project you could use project settings to
manager version of antlr.
Please look at org.eclipse.core.sourceParsers extension point. You could
contribute any set of parsers, and provide selector to choose one required.

If you want to per file configuration then you need to write some custom
management.

As for "clean up" you could call builder to rebuild all for project,
workspace.

Also I would recommend to write custom antlr runtime managment, with
ability to add antlr dynamically.
So for example users could manage runtimes as Tcl interpreters.

Best regards,
Andrei Sobolev.

> Hi Jae,
>
> I want to support both antlr-3.0.1 and antlr-3.1 and I would give the
> chance to the user to select one or another, it's likes java compiler
> compliance level. Then when the user changes the "compiler level" I
> want to excute a "clean up".
>
> Is there any support for this?
>
> Thanks.
>
> On Thu, Apr 3, 2008 at 12:04 PM, Michael Spector <spektom@xxxxxxxxx
> <mailto:spektom@xxxxxxxxx>> wrote:
>
>     Hi,
>
>     One of the options may be: managing different versions of parsers
>     using Composite design pattern in your ISourceParser.
>
>     On Thu, Apr 3, 2008 at 5:50 PM, Edgar Espina
>     <espina.edgar@xxxxxxxxx <mailto:espina.edgar@xxxxxxxxx>> wrote:
>
>         Hi all,
>
>         I'm working on my plugin ANTLRv3 IDE and I want to support
>         antlr-runtime-3.0.1 and antlr-runtime-3.1.
>
>         I would like to have a preference page to select the
>         antlr-runtime (3.0 or 3.1) and when the runtime
>         changes I need to execute a "clean up". Also it could be great
>         if the user can define the antlr-runtime
>         (add *.jar)
>
>         Is there any support or suggestions for this?
>
>         BR
>
>         Edgar
>
>
>
>         _______________________________________________
>         dltk-dev mailing list
>         dltk-dev@xxxxxxxxxxx <mailto:dltk-dev@xxxxxxxxxxx>
>         https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
>
>
>
>     -- 
>     Michael
>     _______________________________________________
>     dltk-dev mailing list
>     dltk-dev@xxxxxxxxxxx <mailto:dltk-dev@xxxxxxxxxxx>
>     https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>