Shulou(Shulou.com)06/03 Report--

This article is about what you know PHP7 needs to pay attention to, the editor thinks it is very practical, so share it with you to learn, hope you can get something after reading this article, say no more, follow the editor to have a look.

Finally, you don't have to see any more prompts advising you not to use the mysql_ function. Because PHP 7 removes them completely from the core, this means moving to a better mysqli_ class function, or a more flexible PDO layer.

two。 Don't write useless code.

This may seem like a mindless suggestion, but as the speed of PHP7 increases, it obscures some problems and makes it increasingly important. Don't be smug just because you cut to PHP7 to make the site faster.

To understand the importance of speed and how to do it better, take a look at our guide to accelerated optimization for beginners in this article.

As a developer, you should ensure that scripts are loaded on demand, recombined when possible, write efficient database queries, use caching if possible, and so on.

3. Do not use PHP closing tags at the end of the file

If you look around, you will find that most of the WordPress core code files have omitted the PHP closing tag at the end. In fact, the Zend framework specifically forbids closed tags. It is not required for PHP, and omitting it at the end of the file ensures that there is no extra white space at the end.

4. Do not quote and pass parameters unless it is necessary.

Personally, I really don't like quoting and passing parameters. I certainly know that it is useful in some situations, but in most cases, it makes the code difficult to understand, difficult to follow, and difficult to predict the results.

People think that references can make their code faster, but as the honorable PHP programmer pointed out in this article, this is not the case.

PHP's built-in shuffle () or sort () function is a bad case of passing references. It modifies the original array instead of returning a scrambled or sorted array, which is completely against our will.

5. Do not use queries in loops

The worst when using database queries in a loop. It puts unnecessary pressure on the system, and it's possible that you can use queries outside the loop to get the same results faster. When I encounter scenarios that have to be used in this way, I usually solve the problem by dividing the query into two queries to construct an array. Then loop through the array without having to loop through the query.

Due to the way WordPress works, there may be some exceptions to this. Get_post_meta () will get a metadata from the database, and if you are iterating through the metadata for a particular article, you can use it in the loop. This is because when you first use it, WordPress actually takes all the metadata and caches it. The subsequent call is actually a call to cached data rather than to the database.

The best way to solve these problems is to read the function documentation and use something like a query listener.

6. Do not use * in SQL queries

Well, it's more like a MySQL problem, but we prefer to write SQL statements in our code, so I say it's a fair game. In any case, if you can avoid using wildcards, don't use them, especially if your database has a lot of fields.

Specify the fields you need and retrieve only those fields. This helps save memory, protect data, and make things clearer.

On the SQL side, learn as much as possible about the functions you can use and test the speed. When calculating averages, sums, and similar numbers, use SQL built-in functions instead of PHP functions. If you are not sure about the speed of a query, test it and compare it with other practices to choose the best one.

7. Do not trust the user's input

It is unwise to trust user input. For user input, you always need to filter, antivirus, escape, validate, and use fallback. There are three problems with user input: it is impossible for us developers to consider all the possibilities, frequent errors, and deliberate malicious input.

A well-considered system can prevent all these problems. When using a database, be sure to use built-in functions, such as filter_var (), to check validity, escape, and other things you can do.

WordPress has a bunch of functions that can help you. You can take a look at this article to learn more about Validating escaping and sanitising user data.

8. Don't be smart.

Your goal is to write elegant code that clearly expresses your wishes. You may have saved 0.01 seconds of loading time per page by shortening variable names, using multi-level trinomial logic operations, and other tricks, but the loss outweighs the resulting headaches for you and your team.

Name variables properly and write code documentation in a concise and straightforward manner. It is better to use a standardized object-oriented code style, more or less documented, rather than a lot of inline code comments.

9. Don't repeat the wheel.

PHP has been around for some time, and website development has been around for even longer. Whatever you have done, your predecessors must have done it. Don't be afraid to rely on the support of others. Github, Composer and Packagist are all your mentors.

From logs to color processors, from analyzers to unit test frameworks, from Mailchimp APIs to Twitter Bootstrap, everything can be used at the touch of a button (or a command). Use them!

10. Don't ignore other languages.

If you are a PHPer, the standard practice now is to know at least HTML,CSS,Javascript and MySQL. When you can handle these languages well, it's time to learn Javascript again. Javascript is not jQuery. You should learn Javascript to make effective use of jQuery.

I also recommend learning everything about PHP object orientation. It is a lifesaver that can improve your code by an order of magnitude. It can also open the door to languages like C # and Java, which can make it easier for you to understand object-oriented programming (OOP) after you have these experiences.

Expand your knowledge through learning package management, build scripts, Coffeescript, LESS, SASS, YAML, template engine, and other useful tools. I also sincerely recommend looking at other frameworks, especially Laravel.

When you've done all this well, consider app development for Ruby, Ruby on Rails, and Android,iPhone,Windows Phone? You may think these are meaningless because they are not within your comfort zone and job needs, but they are precisely the point. Each language has some useful teaching knowledge and some harmless extra knowledge. It's no accident that all top PHP developers know other programming languages!

These are what you know PHP7 needs to pay attention to, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.