Hello Guillaume,
>
> Do you have ideas of what other errors could be detected
> automatically? I
> could only think about unbalanced parenthesis. Maybe other
> syntaxic error
> could be detected by syntaxic parser bundled with the JDE?
Well I can think of various others -
1. If a type name cannot be reached given the list of imports and
the package to which this buffer belongs (this could based on
failure of jde-import-find-and-import defun to import a class).
2. No return value statement in a non-void method.
3. Type mismatch in expressions. This should be possible due to
completion code (which can deduce the type of the expression).
In general if all of us think that this king of development environment
is useful, we can put our minds to it, we could come up
with a framework for doing increamental parsing and such.
The code-aid plugin of jedit has some features along these lines.
Most of my ideal set of features for a Java editor are already
satisfied by JDE. I will like to thank Paul K. for developing
such a wonderful tool.
>
> Other ideas could possibly be obtained from java code audit
> tools such as
> JTest (http://www.parasoft.com/products/jtest/) but I think
> they work mainly
> on code which compiles. Consequently, error/warning they
> submit are maybe
> less interesting during coding, but maybe in a later step?
> There are such
> things as warning about missing code statement for a stream...
Yes.
Sandip V. Chitale 150, Almaden Blvd
work: (408) 535 1791 ext: 791 San Jose, CA, USA
email: [EMAIL PROTECTED] 8th floor, Cube 831
web: http://L064-5440.blazesoft.com
