[clug] java tools (fwd)
sjenkin at canb.auug.org.au
Wed Mar 3 00:22:37 GMT 2004
I asked a mate who's business is Java [Responsive Systems].
Here's his reply edited down.
He made the offer to come in and help with reviews and other help.
A competent, experienced person being way better than any tool.
I can put you in touch if you're interested.
It's not the job of the compiler to perform a structural analysis of the
code, and I've got little faith in many automated tools. They'll only
pick up the simple things which will at worst increase memory footprint by
a few bytes.
My recommendation is code review and extensive documentation. Depending
on the size of the projects, UML or CASE tools might help them or just
gcj, the gcc java compiler also may help, but I've never used it.
I'd say again, code review and documentation (inline) will be their best
bet of improving code quality.
Running javadoc over your source tree is the best way to view and enforce
a consistent API for the modules, which is generally more important than
unused var's or loop invariants.
My 2c. Other than that, tell him to hit google or sourceforge.
>---------- Forwarded message ----------
>Date: Tue, 02 Mar 2004 21:32:02 +1100
>From: Eyal Lebedinsky <eyal at eyal.emu.id.au>
>To: CLUG list <linux at lists.samba.org>
>Subject: [clug] java tools
>At work, we want to improve our java code. Sun jdk does not give enough
>warnings (like unused vars and what not).
>We want tools to inform us of bad programming, suspect code and
>evenplain unusuak constructs.
>Eyal Lebedinsky (eyal at eyal.emu.id.au) <http://samba.org/eyal/>
Steve Jenkin, Unix Sys Admin
0412 786 915 (+61 412 786 915)
PO Box 48, Kippax ACT 2615, AUSTRALIA
More information about the linux