Comments on: Code Analyzers

By: Preeti desai

Preeti desai — Sat, 04 Dec 2004 21:42:16 +0000

Im writing a simple program in Java to read from MSAccess and transfer the same to Excel sheets.
MSAccess database contains huge “text” as one of its fields. and After transer, im getting some junk characters in output wherever there is a newline orcarriage return. can anyone tell me how to eliminate those junk characters from my output file.

Thanks
Preeti

By: newsfeed.choas.net

newsfeed.choas.net — Wed, 26 Nov 2003 22:53:06 +0000

[Trackback] Code Analyzers

Jalopy is a source code formatter for the Sun Java programming language.

PMD scans Java source code and looks for potential problems…

Checkstyle is a development tool to help programmers write Java code that adheres to a codin…

By: Steve

Steve — Wed, 22 Oct 2003 08:33:29 +0000

You might want to try out IDEA (IDE from JetBrains) as it has most of the functionality you describe built in.

By: Padraic Kinsella

Padraic Kinsella — Wed, 22 Oct 2003 02:06:25 +0000

This one costs money but has an extensive range of audits and metrics which are configurable

http://www.bluebaysystems.com/products.htm

Also, Eclipse is quite nice at detecting and highlighting common problems as mentioned above you edit, such as unused local variables, parameters and private methods, empty catch blocks

By: Jean Tessier

Jean Tessier — Tue, 21 Oct 2003 21:32:50 +0000

Dependency Finder is an open source tool for analyzing compiled Java and track inter-dependencies down to the method level. It can also show aggregated views at class and package level, and pinpoint specific items with regular expressions. The toolkit includes an API diff tool, for comparing succesive versions, and an embryonic OO metrics tool. It may not be as fully integrated with IDEs as the commercial competition, but it’s FREE.

By: Debashish

Debashish — Tue, 21 Oct 2003 08:42:18 +0000

Thanks for your input guys. Few more tools (not free though) are JStyle and JProbe but the latter demands a standalone application or atleast one class in the package that has main method. For testing your custom API classes or for testing individual classes I think a combination of PMD + CheckStyle + Findbugs would be all you need. JStyle is also cool and comes with a detailed help document that explains each coment with code examples.

By: Graham

Graham — Tue, 21 Oct 2003 08:07:32 +0000

JLint is *really good* for finding dodgy code.
It can identify potential synchronization deadlocks from source files as well as picking up a whole mountain of potential problems that the human eye just wouldn’t see.

By: Venkatesh S

Venkatesh S — Mon, 20 Oct 2003 18:10:01 +0000

Check out JDepend too. Pretty good one for metrics.

By: Anonymous

Anonymous — Sat, 18 Oct 2003 15:04:06 +0000

The CVS version of checkstyle also has many metrics such as cyclomatic complexity, etc. There is also a tool called simian a colleage of mine showed me which checks for copy and pasted code. PMD also has a tool called CPD for finding copy and pasted code.