RE: [jdt-ui-dev] Refactoring: Any plans for a Lint like tool (...a tool

[Scott Stanchfield <scott@xxxxxxxxxxxx>]

There's nothing wrong with using ANTLR for a tool like this ;)

(I used to work for Terence Parr, its creator, and I'm looking at porting my
ANTLR debugger, ParseView, to Eclipse at some point ;)

Sure, someone could write a tool that uses the Java AST support in Eclipse,
but then that tool would only be useful inside Eclipse. Some fo the tools
like this I've seen (javacheck, for example, and the auditing tools in
Instantiations' CodePro Studio) target other environments, and decide to use
other tools like ANTLR.

Of course, one could make the argument that Eclipse reinvents several
wheels. Even so, where's the inherent harm?
-- Scott

==============================================================
Scott Stanchfield    scott@xxxxxxxxxxxx    http://javadude.com

Lead author of "Effective VisualAge for Java, Version 3"
                                      http://javadude.com/evaj

VisualAge for Java Tips and Tricks     http://javadude.com/vaj
Visit for Java Enlightenment!             http://www.jguru.com
==============================================================

> -----Original Message-----
> From: jdt-ui-dev-admin@xxxxxxxxxxx
> [mailto:jdt-ui-dev-admin@xxxxxxxxxxx]On Behalf Of Valentino Kyriakides
> Sent: Tuesday, December 03, 2002 5:57 PM
> To: jdt-ui-dev@xxxxxxxxxxx
> Subject: AW: [jdt-ui-dev] Refactoring: Any plans for a Lint like tool
> (...a tool to identify bad code smells...)?
>
>
> Thank's for the infos.
>
> I know that there are a bunch of third party tools like Java syntax/code
> checkers etc. which partially offer a subset of these features. However,
> these often use an own underlayed parser engine (mostly ANTLR or JavaCC
> based) and thus would somehow reinvent the wheel here for
> Eclipse. - I will
> make a search after that "Tallyho from Carnegie Mellon" Adam
> mentioned, just
> in order to see what this offers or might be at all (BTW, never
> heard before
> of that Tallyho...).
>
> -Valentino
>
> > -----Ursprüngliche Nachricht-----
> > Von: jdt-ui-dev-admin@xxxxxxxxxxx
> > [mailto:jdt-ui-dev-admin@xxxxxxxxxxx]Im Auftrag von Adam Kiezun
> > Gesendet: Dienstag, 3. Dezember 2002 23:43
> > An: jdt-ui-dev@xxxxxxxxxxx
> > Betreff: Re: [jdt-ui-dev] Refactoring: Any plans for a Lint like tool
> > (...a tool to identify bad code smells...)?
> >
> >
> > > Are there any future plans for a Lint like tool, similar to the
> > one which
> > > comes with the Smalltalk Refactoring Browser?
> >
> > Nope, there are only plans until 2.1 and all of that is on the website.
> > There are commercial plugins that offer that kind of functionality.
> > There are also research plugins that do that (e.g. Tallyho from Carnegie
> > Mellon - see earlier posts from Timothy Halloran).
> >
> > Thanks for the input - we are always open to ideas. This one will
> > be considered
> > too, but only after 2.1 I'm afraid.
> > a.
> >
> > _______________________________________________
> > jdt-ui-dev mailing list
> > jdt-ui-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev
> >
>
> _______________________________________________
> jdt-ui-dev mailing list
> jdt-ui-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev
>