PHP programming style_PHP tutorial

Original author: Tim Perdue
Source: www.phpbuilder.net
In many cases, the most valuable feature of PHP may also be its weakest link is its loose syntax. PHP is so widely used because it enables many inexperienced Web developers to create powerful applications without having to worry too much about planning, consistency, and documentation.
Unfortunately, due to the above characteristics, many PHP source codes are bloated, difficult to read and even impossible to maintain. I understand this deeply because I have written a lot of this code. ;-)
In order to avoid the above situation and many other situations. Many core PHP developers and community members came together and started PEAR, a project focused on increasing the PHP extension and plug-in repository. As of now, the documentation and other content from the PEAR project is sparse and difficult to understand. This article attempts to tell the developers what they (the PEAR team) are doing.
An important factor that determines the maintainability of code is the format and comments of the code. All code for a project should be organized in a coherent manner. I'm a stickler for the code base, and I think programmers should be too.
(1) Indentation
All developers’ code should be written completely in an indented manner. This is the most basic measure to improve code readability. Even if you don't comment your code, indentation can be a huge help in making your code easier for others to read.
For example:
while ($x if ($a == 1) { echo A was equal to 1;
} else {
if ($b == 2) {
//do something
} else {
//do something else
}
}
}
PEAR Draft Standard Requirements Use 4 spaces for indentation instead of tabs. I personally don't agree with this point of view, I think I will still continue to use the tab key. I think using tabs makes the file smaller than multiple spaces. And smaller files can be interpreted, uploaded, downloaded, etc. faster. Another big advantage of using tab is that when viewing other people's code, you can set the number of spaces for the tab key yourself. I usually use a tab key setting with a length of 8 spaces, but recently changed it to a length of 4 spaces. Haha, I call it code reformatting, just a personal hobby.

(2) Control structure
This largely depends on personal taste. I can still see a lot of control structure code without branch statements, resulting in very poor readability. If you use IF statements without branches, not only will the readability become worse, but when other people modify your program, it will also cause Lots of bugs. Look at the following example:
Bad example:
if ($a == 1) echo A was equal to 1;
This is very illegible. It will work, but no one will appreciate it except you.
An improved example:
if ($a == 1)
echo A was equal to 1;
Now at least this code is readable, but it is still not very maintainable. sex. What if I want an additional event to occur when $a==1, or need to add a branch? If later programmers forget to add braces or else keywords, bugs will appear in the program.
Perfect example
if (($a == 1) && ($b==2)) {
echo A was equal to 1;
//It is easy to add other codes
} elseif (($a == 1) && ($b==3)) {
//Other operations
}
Please note the spaces after if and elseif, this will This statement is distinguished from a function call. In addition, although there are no statements in the elseif execution section, only comments, which may appear redundant on the surface, but it gives a very convenient tip to programmers who will maintain the program in the future, and is very conducive to adding functions. .
Source: osso.com

http://www.bkjia.com/PHPjc/531830.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/531830.htmlTechArticleOriginal author: Tim Perdue Source: www.phpbuilder.net In many cases, the most valuable feature of PHP may also be Its weakest link is its grammatical looseness. PHP can be used so widely...