Home  >  Article  >  Backend Development  >  Is it still useful to stop updating php?

Is it still useful to stop updating php?

(*-*)浩
(*-*)浩Original
2019-09-17 11:35:123804browse

According to the supported versions and schedule listed on the PHP official website (below), PHP 5.6 was released in 2014. Main support was closed on January 19, 2017, and security support will be closed on December 31, 2018. End date.

Is it still useful to stop updating php?

In fact, the major and security update period of PHP 5.6 has ended long ago, but due to the large number of websites used, the PHP maintenance organization has At one point, their support hours were respectively extended. (Recommended learning: PHP programming from entry to proficiency)

Some people describe this situation as a PHP time bomb. The newer PHP 7.0 will no longer have security support at EOL (End of Life) on December 1st this year. Even version 7.1 will reach end of life on December 1st. Security support ends after one year.

Now the latest officially released version is php7.2 and the php6 version has been skipped and directly ushered in php7.

Some features of php7

Breaking everything

PHP7 is going to break everything. PHP developers should accept the law of breaking backward compatibility between versions. As long as extensive backward compatibility is not allowed, PHP7 will be a highly respected language.

1. Create a specific core language. Remove all library methods and keep the core methods in the object set. You should be able to write PHP7 without any external libraries or extensions and a nice complete language for basic input/output, string handling and math. Any extension outside of the library should be approved.

2. Treat everything as an object. Take objects from Ruby, Smalltalk, and (mostly) Java, and treat everything as an object. Integers are objects, strings are objects, and each of them has methods that can be manipulated. I don't believe that PHP needs the notion of Ruby and Smalltalk to pass messages between objects, and calling methods on objects is the best.

3. Consistently name methods and classes. One of the biggest complaints about PHP is constantly having to check, (needle,haystack) or (haystack, needle), or some_function(), or function_some(), or someFunction(), a consistent format needs to be developed.

4. To make things strictly try passing a float string into a method? This is a warning.

5. Everything is Unicode. All strings in PHP6 are Unicode, which is good. I advocate that PHP7 should also be maintained.

6. Central startup point Create a main class or initialization from which all code execution originates.

7. Clean up C code. I am not an expert in C, but if you know more about Ruby's C code and PHP's C code, you can easily understand the internals of PHP and Ruby. I'm very familiar with PHP, so writing my own extension is easier.

8. Get rid of eval() eval() is evil. If you are using it then this is a wrong idea: this will break PHPUnit, discard it from now on.

9. Support operator overloading. Because everything is an object, developers only need to master the methods of operating objects.

10. Allowed method signatures

The above is the detailed content of Is it still useful to stop updating php?. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn