[antlr-interest] Spoiled windows brat reporting
Tiller, Michael (M.M.)
mtiller at ford.com
Tue Oct 26 07:33:07 PDT 2004
Another feature of the Eclipse plug-in the I find extremely useful is
the outline mode. This allows you to see a list of rules and jump
directly to them in the file.
--
Mike
> -----Original Message-----
> From: Alexey Demakov [mailto:demakov at ispras.ru]
> Sent: Tuesday, October 26, 2004 6:27 AM
> To: antlr-interest at yahoogroups.com
> Subject: Re: [antlr-interest] Spoiled windows brat reporting
>
>
> > > There is Eclipse plugin for ANTLR that hides command line and
improves
> readability of grammar file.
> > > But parser creation requires some coding anyway :)
> >
> > Although I have downloaded Eclipse I haven't had the time (or
> motivation) to play with it yet. Right now I've added ANTLR as a
> pre-build event to the C# project, so that I can use that IDE for
editing
> the grammar as well as reviewing the generated source.
> >
> > Thanks for the tip though, I might try it later when I get the hang
of
> all this other stuff (so many new things coming at me at
> once ;)). Could you give a small review as to what the Eclipse (with
ANTLR
> plugin) does exactly (ie: how does it hide the cmd line,
> improve readability, will it help me with debugging my grammar, etc.?)
>
> The main features of ANTLR Eclipse plugin are:
> 1. Syntax highlighting in *.g files
> 2. Compiling grammars from context menu - no command line. Output
folder
> and super grammar properties
> can be specified in file properties dialog.
> 3. Errors and warnings occured when compiling grammars are shown in
> Eclipse Problems dialog.
>
> Generated lexer/parser can be debugged at Java level in Eclipse visual
> debugger - it's enough for me.
> But of course source-level debugging sounds very interesting :)
>
> If you develop for .NET platform, Eclipse only for ANTLR is not
optimal
> choice. I edit grammars in VS.NET editor
> and compile them in pre-build events. Lack of syntax highlighting is
> annoying but not critical.
> Unfortunately in VS.NET there is no way to specify keywords for
> highlighting (as it was in VS6).
> Writing addins for VS.NET is much more complicated :(
>
> Regards,
> Alexey
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/antlr-interest/
<*> To unsubscribe from this group, send an email to:
antlr-interest-unsubscribe at yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
More information about the antlr-interest
mailing list