DoitPHP Coding Specification 1. Introduction This specification is based on programming principles such as PHP PEAR coding specification and PHPDocumentor annotation specification. It integrates and refines the mature experience accumulated by developers over a long period of time and is intended to help form a good and consistent programming style. To achieve twice the result with half the effort. In order to keep pace with the times and based on objective needs, this document will be updated from time to time. Author: tommy < streen003@gmail.com > Copyright: DoitPHP Group < www.doitphp.com > Update date: September 25, 2010 2. Scope of application Unless otherwise specified, the following rules and requirements are fully applicable to DoitPHP Project (Note: Doitphp's PHP framework file, not the PHP project developed using DoitPHP). If you like the following coding standards, you can also use them in other PHP development projects. 3. The Importance and Benefits of Standardization "No rules, no rules." When the development of a software project adheres to public and consistent standards, the entire team members form and maintain a consistent coding style, and the entire project document is written by one person. Each programmer's code is easy to understand for others, improving the maintainability of the code and thus reducing the maintenance cost of the software. At the same time, new participants can quickly adapt to the environment, thereby maximizing the efficiency of team development cooperation. Long-term standardized coding can also allow developers to develop good coding habits, reduce the chance of coding errors, and even develop more rigorous thinking. The purpose of "documenting" the specifications is to clarify our coding standards. We believe that standards are not the key to project success, but they can help us be more efficient in team collaboration and complete set tasks more smoothly.