update : 2015.11.03
php.shukuma.com검색:
|
Backward Incompatible ChangesAlthough most existing PHP 5 code should work without changes, please take note of some backward incompatible changes: Windows XP and 2003 support droppedSupport for Windows XP and 2003 has been dropped. Windows builds of PHP now require Windows Vista or newer. Case insensitivity no longer locale specificAll case insensitive matching for function, class and constant names is now performed in a locale independent manner according to ASCII rules. This improves support for languages using the Latin alphabet with unusual collating rules, such as Turkish and Azeri. This may cause issues for code that uses case insensitive matches for non-ASCII characters in multibyte character sets (including UTF-8), such as accented characters in many European languages. If you have a non-English, non-ASCII code base, then you will need to test that you are not inadvertently relying on this behaviour before deploying PHP 5.5 to production systems. pack() and unpack() changesChanges were made to pack() and unpack() to make them more compatible with Perl:
Writing backward compatible code that uses the "a" format code with unpack() requires the use of version_compare(), due to the backward compatibility break. For example:
<?php self, parent and static are now always case insensitivePrior to PHP 5.5, cases existed where the self, parent, and static keywords were treated in a case sensitive fashion. These have now been resolved, and these keywords are always handled case insensitively: SELF::CONSTANT is now treated identically to self::CONSTANT. PHP logo GUIDs removedThe GUIDs that previously resulted in PHP outputting various logos have been removed. This includes the removal of the functions to return those GUIDs. The removed functions are:
Internal execution changesExtension authors should note that the zend_execute() function can no longer be overridden, and that numerous changes have been made to the execute_data struct and related function and method handling opcodes. Most extension authors are unlikely to be affected, but those writing extensions that hook deeply into the Zend Engine should read the notes on these changes. |