[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-core-dev] Re: What should Eclipse compiler default settings be ?
|
If we did comply with javac, we would:
- not report methods overridden but not package visible
- not report methods with a constructor name
- not report hidden catch blocks
- would report deprecation inside deprecated code
as we currently do today.
The error level must comply with the JLS and javac by default, but the
warning level is ours. We can provide more warning info to flag common
mistakes, and based on common mistakes we propose to enrish the warning
level.
I personally think unused local variables can be useful for debug
purpose...
More advanced notifications could be provided by a QA tool, which our
compiler isn't (in ST, this was a separate tool). If we had time to
investigate such a tool, then I agree most of our compiler warning
diagnosis would no longer be necessary.
celek@xxxxxxxxxx
Sent by: To: jdt-core-dev@xxxxxxxxxxx
jdt-core-dev-admin@ cc:
eclipse.org Subject: Re: [jdt-core-dev] Re: What should Eclipse
compiler default settings be ?
10/16/2002 03:56 PM
Please respond to
jdt-core-dev
+1 for unused imports and unused local variables as warning [i also set the
options like this]
but... i do that at the end of the development cycle (when about to
release)
so I can clean the code.
Agree with Jeem that we should show the exact same warning as javac, but I
also agree with Olivier (I agree with too many people today :-) that it is
useful to clean you code... can we move the warning as part of a 'clean
code' that could analyze bad coding structure, override that do not call
super and so on (I believe we had such in the smalltalk ide)
--
Christophe Elek
Eclipse.org (Platform Update)
(905) 413-3467
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
