There are many programming specifications available for reference on the Internet, and many companies have developed their own Code compiling specifications. But do we always write according to the programming specifications? In the face of a large amount of code, we need to use an effective tool to check the code standardization.
Through a book introduction, I learned about Borland's Together tool, which can review the code quality, refer to the problematic Code and provide correct comments and instructions. For example, you can perform the following operations to check a code file:
1. Create Together support for the project
2. Select the class to be reviewed under Model View (after the Together tool is installed, you can open the Model View in the attempt menu of VS. NET)
3. Find the problematic code
4. view the reason
5. Oh, it turns out that the if statement needs to use {}
In fact, there are more code requirements that you can take a look. After all, this is just a tool, and you cannot rely on it completely. However, it is helpful to check your programs frequently. With this tool, you can review your own code at any time and find out the cause by referring to the instructions. Soon, you can consciously form a good programming specification and Compile High-Quality code. This tool can also be used to measure the Code (Code Metrics) and determine whether the quality of the program Code can be improved based on the measurement results.
This tool also provides support for UML functions, but I will not talk about it any more. We provide three links for your reference:
Together and Visual_Studio_NET combined use (a): http://www.51cto.com/html/2005/0901/2282.htm
Together and Visual_Studio_NET combined use (2): http://www.51cto.com/html/2005/0901/2283.htm
Use Together with Visual_Studio_NET (3): http://www.51cto.com/html/2005/0901/2284.htm
Related urls:
Http://www.borland.com/us/products/together/index.html
For. NET users. It provides two versions of Together Designer 2005, for. NET 2003 and Together Developer 2005, for. the NET 2003 version seems to be similar. I have not carefully read the instructions yet, so I should choose either of them.