Shulou(Shulou.com)06/02 Report--

This article introduces you how to easily and effectively check the Java program code, the content is very detailed, interested friends can refer to, hope to be helpful to you.

The most boring part of the Java project, which programmers always avoid, is checking the Java code. It's really painful to check thousands of lines of other people's code for block parentheses, code indentation, Javadoc comments, and naming conventions. To make matters worse, code reviews are often limited by pressing project schedules. There is not enough time to evaluate the details of the code, so code review often becomes a beautification exercise for the code. No matter how well-intentioned the inspectors are, optimization and logic checks take a back seat.

The Java program code analyzer relieves this pain.

In the face of this situation, the Java program code analyzer is the right medicine. These tools automate the code review process as much as possible. All that is left for the human to do is to examine the defects of the class and the core logic and determine possible optimization methods. Optimization (removing unnecessary instantiated objects, checking that database connections are reasonable, and ensuring that data is cached where possible) usually leads to significant performance improvements for any code.

I've been exposed to all kinds of code analyzers recently. I think a basic and most important function is integration with commonly used IDE (such as NetBeans, Eclipse, jEdit, and JDeveloper). There are some code review tools that are effective at finding errors, but they require you to manually track errors based on the line number of the error given. Such a tool is too tiring to use. Tools integrated with the IDE environment can greatly simplify this process because the results of the code review are displayed by the IDE used. You only need to double-click on the error to reach the line of the error code in the Java editor.

My trial experience

Among the tools I have tried, I have found that three of them are very powerful and conform to the standards for integration with IDE: PMD, Checkstyle, and Jalopy.

PMD and Checkstyle

According to PMD's documentation, ◆ examines the following parts of the code:

Unused local variables in ◆

◆ empty catch block

◆ does not use parameters

◆ empty if statement

◆ duplicate import statement

Private methods not used by ◆

◆ may be a class of Singletons

◆ short / long variable and method name

◆ Checkstyle checks the following sections:

◆ Javadoc comments

◆ naming convention

◆ title

◆ Import statement

◆ volume size

◆ blank

◆ modifier

◆ block

◆ mixed check (including some useful ones such as unnecessary System.out and printstackTrace)

Their role.

Unlike PMD,Checkstyle, which can check Javadoc comments, PMD provides a useful feature called CPD, which checks the copy-and-paste portion of the code. The most frequent errors I find with PMD are unused import statements, unused private variables, and accidental repeated spelling. Checkstyle can find more errors. This includes missing Javadoc comments, lines of more than 80 characters, irregular variable names, using tab instead of spaces, and so on. Both tools allow you to create custom rules.

If you want to use one of them in your organization, Checkstyle seems to be better: it examines most of the projects agreed upon by the company code. If improving code quality is the primary goal, then PMD is a good choice. But if you want more functionality and actually use tools to modify the code, you should try Jalopy.

Jalopy

Jalopy is an easy-to-configure source code format that detects and fixes a large number of habitual defects in Java code. Jalopy is more like a code cleaner than an inspector. Jalopy plug-ins now support most IDE, and most of them are seamlessly integrated. I find that Jalopy is very strong and can do a lot of cool things. For example, it can modify code indentation, align parentheses, make the line width match a character length, insert relevant Javadoc comments, and sort import statements. The place of Jalopy*** is the super custom function. A simple user interface allows you to select switches for all the functions of Jalopy without the need for a XML configuration file.

Don't waste resources.

I suggest you use these tools to replace manual code reviews that are time-consuming and laborious with little success. Once you use these tools to make code review a relatively easy task, you can treat code review as a normal task rather than something you do at the end of the project when you are in a mess. These tools also provide integration with Apache Ant, so you can run these code inspectors every day and work well when compiling or executing unit tests. Control your Java code and deliver what you really think is of high quality.

On how to easily and effectively check the Java program code to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.