Some methods for analyzing php source code

 

I recently analyzed the daily group buying source code, but various require_once causes me to crash, so I found some online

 

Source program analysis method. See

 

I. First, install the source code, and combine its documents and manuals to familiarize yourself with its functions and application methods.

II. View the directory structure of the source code to understand the functions of each directory.

3. After the above two steps, I believe you have a preliminary understanding of this open-source product. Now let's analyze its source code. In this step, we start to analyze the source code framework. For example, if the portal is a single portal or multiple portals, you can find the pages used by a function based on the calling rules between pages.

4. Familiar with the source code writing style, such as indentation and typographical format.

5. Familiarize yourself with the databases and tables used in the source code. You can refer to its technical support documentation.

Sat. After the above steps, I believe that you have a better understanding of the source code, but this understanding is only superficial. Let's analyze it from six aspects:

1. Portal construction and implementation of page calling methods. If you see tool classes and tool functions during reading, try to familiarize yourself with them. In this step, you can learn the source code system architecture.

2. Analyze the tool classes and tool functions used in the source code, so that you can learn a lot of programming skills. You can improve your programming skills.

3. Combined with some security rules, study how the source code implements the security design. In this way, you can improve your awareness and skill in security.

4. If there is a template engine, study the source code template engine. This article focuses on implementation methods, efficiency, and usability.

5. Study the various functional modules of the system, so that you can learn programming skills and open your own programming ideas. The next time you encounter something similar, you will have a good idea.

6. The design patterns used by the research system are similar to those used for implementation of the same functions. The design patterns used may differ a lot. Compared with the previous Dongdong analysis and design patterns, this is the best way to improve our control of code.

7. Study source code optimization on access pressure, execution efficiency, system efficiency, and database query.

The method is only a means and a tool, and your efforts are also required for specific practices. Don't worry, analyze it carefully, and use your analysis experience on your specific project!

 

From Zhang yaner's blog