Phased summary of project research Phased summary of good PHP coding style

This article summarizes the style of good PHP code and shares it with everyone for your reference. The details are as follows:

1. Avoid using magic numbers

if($age<18){
}

I don’t quite understand why this 18 is like this.

You can define 28 in a variable. The name of this variable indicates the meaning of the value

$adult_age = 18;//成年的分界点年龄
if($age<$adult_age){
}

2. The return result of the function: Do not use a variable to store the return result

Once you know the return result, Should return immediately. The advantage of doing this is that it can reduce errors.

3. Functions have many parameters. No more than three

If there are many parameters, try to aggregate them into one model and pass them in. For example, an array or an instance can be used.

Why do too many parameters affect the stability of the method?

For example, modification will become very troublesome.

I understand now. This method needs to add a new parameter to pass in, so the code that originally called this method must be changed accordingly.

When making interfaces, we often encounter similar problems.

function forgot($userName, $email, $email_url, $format = 'json')

The above are the three parameters.

It turns out that when someone else calls this function,

forgot($userName, $email, $email_url, $format = 'json');

Now the requirements have changed and a new parameter needs to be added. What should I do?

The original code needs to be modified accordingly. The method is not stable. Or open a new method to adapt to new needs. Or modify the calling code of the caller.

But there is a way to avoid this problem

Make the original passed parameters into an array, as follows:

forgot($params=array(),$format = 'json');

Aggregate them into an array. You can add as many parameters as you like.

How to understand: What about the built-in functions of the php engine with multiple parameters?

Design flaw?

4. The parameters of the method contain Boolean parameters.

This means that this method does not accomplish a single goal. Violation of single responsibility. Added complexity.

Leave it to everyone to think: How to understand the problems in our current code

Readers who are interested in more PHP-related content can check out the special topics on this site: "Introduction Tutorial on PHP Object-Oriented Programming", "Summary of PHP Mathematical Operation Skills" ", "Summary of PHP operating office document skills (including word, excel, access, ppt)", "Complete PHP array (Array) operation skills", "PHP data structure and algorithm tutorial", "php programming algorithm summary", " PHP regular expression usage summary" and "php common database operation skills summary"

I hope this article will be helpful to everyone in PHP programming.

The above introduces the phased summary of project research and the phased summary of PHP good coding style, including the phased summary of project research. I hope it will be helpful to friends who are interested in PHP tutorials.