[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Java compiler defaults changed
|
On the unused imports, heres some empirical data for I collected on
Eclipse and some other (well-known) Java code (this has been floating
around the jdt-ui-dev mailing list for some time):
| import | UNUSED IMPORTS |
Name | Uses(u) | # | %u | /kSLOC | kSLOC
---------------------+---------+-------+------+--------+------
Jakarta Ant 1.5 | 3,526 | 172 | 4.9 | 2.7 | 64
Jakarta Tomcat 4.0.4 | 4,275 | 966 | 22.6 | 14.6 | 66
Sun J2SDK 1.4.0_01 | 15,101 | 3,216 | 21.3 | 6.3 | 508
NetBeans 3.2.2 | 30,102 | 6,626 | 22.0 | 11.6 | 571
ECLIPSE 2.0 | 49,097 | 2,859 | 5.8 | 3.6 | 792
I removed the NetBeans test infrastructure (which is quite involved)
from the analysis (I was using Eclipse so I had to get NetBeans to build
within Eclipse, which was lots of fun:-).
Lets hope this number goes to 0 for Eclipse in 2.1!
Take Care
Tim Halloran
Carnegie Mellon University
On Tue, 2002-10-22 at 07:04, Philippe Mulet wrote:
> FYI - from this integration build on, you'll notice that the Java compiler
> defaults will have changed to report 2 extra warnings:
> - static members accessed in non-static way (e.g. this.CONSTANT).
> - unused imports (often resulting from codeassisting).
>
> If you see these, you should consider fixing them so as to improve your
> code quality.
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
