PHP540 ChangeLog (part 1)

: This article mainly introduces the ChangeLog version PHP540 (I). If you are interested in the PHP Tutorial, please refer to it. Preface

With a large number of frameworks using composer and namespace, the online environment gradually changed from 5.3 to 5.4, 5.5, or even 5.6. with the release of PHP7 in May, more companies will adopt new versions.

I have been writing such an article for a long time to illustrate the differences between different versions. this is time.

This is the first article. Currently, we plan to write three articles.

• PHP5.4.0
• PHP5.5.0
• PHP5.6.0

One is to organize your own knowledge, and the other is to improve yourself.

Official description

Official document address http://php.net/ChangeLog-5.php#5.4.0

Detailed description

01 Mar 2012

Original

• Autoconf 2.59 + is now supported (and required) for generating the configure script with./buildconf. Autoconf 2.60 + is desirable otherwise the configure help order may be incorrect.

Translation

Autoconf 2.59 + now supports (required) generation of the configuration script/buildconf. Autoconf 2.60 + is the ideal configuration, otherwise it may be incorrect.

Autoconf

The dependent software required for php compilation and installation, so the new version of the corresponding supporting software must be replaced with the latest one, which is guaranteed in terms of performance ~

Features Removed From Removed legacy features

Original

• Break/continue $ var syntax.
• Safe mode and all related ini options.
• Register_globals and register_long_arrays ini options.
• Import_request_variables ().
• Allow_call_time_pass_reference.
• Define_syslog_variables ini option and its associated function.
• Highlight. bg ini option.
• Session bug compatibility mode (session. bug_compat_42 and session. bug_compat_warn ini options ).
• Session_is_registered (), session_register () and session_unregister () functions.
• Y2k_compliance ini option.
• Magic_quotes_gpc, magic_quotes_runtime and magic_quotes_sybase ini options. get_magic_quotes_gpc, get_magic_quotes_runtime are kept but always return false, without raises an E_CORE_ERROR.
• Removed support for putenv ("TZ =...") for setting the timezone.
• Removed the timezone guessing algorithm in case the timezone isn't set with date. timezone or date_default_timezone_set (). Instead of a guessed timezone, "UTC" is now used instead.

Translation

• Break/continue $ var syntax.
• Security mode and all associated INI options.
• Register_globals and register_long_arrays INI options.
• Import_request_variables ().
• Allow_call_time_pass_reference.
• Define_syslog_variables INI options and related functions.
• Highlight. bg INI option.
• Session error compatibility mode (session. bug_compat_42 and session. bug_compat_warn INI options ).
• Session_is_registered (), session_register (), and session_unregister.
• Y2k_compliance INI option.
• Magic_quotes_gpc, magic_quotes_runtime and magic_quotes_sybase INI options. Get_magic_quotes_gpc, get_magic_quotes_runtime is saved, but false is always returned. set_magic_quotes_runtime triggers e_core_error.
• Putenv ("TZ = ..") is no longer supported to set the time zone.
• If you do not set the time zone and the time zone date. timezone or date_default_timezone_set (), remove the prediction algorithm. Instead of the estimated time zone, "UTC" is now used instead.

I am using Baidu translation. can I make a fuss? ===

Break/continue

Removed the break/continue $ var syntax.

Before MySQL 5.4, we can pass the following parameters to control the loop of several layers that exit or stop. However, this feature is removed after version 5.4.0.

break$c;continue$c;

Break and continue accepts a number, that specify the number of nested loops, that shocould be breaked up, or continued.

References

• Http://stackoverflow.com/questions/6517401/what-is-the-break-continue-var-syntax-will-be-removed-in-php-5-4
• Http://php.net/control-structures.break

Safe mode and all related ini options. remove the security mode and the options in the configuration file.

The PHP Security mode is set up to solve the shared-server security problem. In terms of structure, it is unreasonable to try to solve this problem on the PHP layer, but it is unrealistic to modify the web server layer and operating system layer. Therefore, many people, especially ISP, currently use the security mode.

The development of language is constantly improving. it is also a process of continuous trial and error correction. Pai_^

• Security measures and security mode, that is, all safe_mode-related configuration items in php. ini are removed.
• Functions restricted or blocked by the security mode. In security restriction mode, some functions cannot be used. This restriction will also be removed.

References

• Http://php.net/manual/zh/features.safe-mode.php

Register_globals and register_long_arrays ini options.

These two configuration items are removed because of the performance relationship.

References

• Http://php.net/manual/zh/ini.core.php#ini.register-globals

Import_request_variables ()

Import_request_variables-import GET/POST/Cookie variables to the global scope

Bool import_request_variables (string Types [, string

The above section introduces the ChangeLog version of PHP540 (I), including some content, and hopes to help those who are interested in PHP tutorials.