下位互換性のない変更点

Modified: phpdoc/ja/trunk/appendices/migration71/incompatible.xml =================================================================== --- phpdoc/ja/trunk/appendices/migration71/incompatible.xml 2017-01-20 00:02:06 UTC (rev 341739) +++ phpdoc/ja/trunk/appendices/migration71/incompatible.xml 2017-01-20 00:38:53 UTC (rev 341740) @@ -1,6 +1,6 @@ - + 下位互換性のない変更点 @@ -263,7 +263,7 @@ - + 参照による代入で自動的に作られる配列の要素の並び順の変更 @@ -308,7 +308,7 @@ - + 同値な要素の並び順内部的なソートアルゴリズムが改良されたことに伴って、 @@ -322,6 +322,250 @@ + + Error message for E_RECOVERABLE errors + + The error message for E_RECOVERABLE errors has been changed from "Catchable + fatal error" to "Recoverable fatal error". + + + + + $options parameter of unserialize() + + The allowed_classes element of the $options parameter of + unserialize is now strictly typed, i.e. if anything + other than an array or a boolean is given, + unserialize() returns &false; and issues an E_WARNING. + + + + + DateTime constructor incorporates microseconds + + DateTime and DateTimeImmutable + now properly incorporate microseconds when constructed from the current time, + either explicitly or with a relative string (e.g. "first day of next + month"). This means that naive comparisons of two newly created + instances will now more likely return &false; instead of &true;: + + + +]]> + + + + + + + Fatal errors to <classname>Error</classname> exceptions conversions + + In the Date extension, invalid serialization data for + DateTime or DatePeriod classes, + or timezone initialization failure from serialized data, will now throw an + Error exception from the + __wakeup or __set_state + methods, instead of resulting in a fatal error. + + + + In the DBA extension, data modification functions (such as + dba_insert) will now throw an + Error exception instead of triggering a catchable + fatal error if the key does not contain exactly two elements. + + + + In the DOM extension, invalid schema or RelaxNG validation contexts will now + throw an Error exception instead of resulting in a + fatal error. Similarly, attempting to register a node class that does not + extend the appropriate base class, or attempting to read an invalid property + or write to a readonly property, will also now throw an + Error exception. + + + + In the IMAP extension, email addresses longer than 16385 bytes will throw an + Error exception instead of resulting in a fatal error. + + + + In the Intl extension, failing to call the parent constructor in a class + extending Collator before invoking the parent methods + will now throw an Error instead of resulting in a + recoverable fatal error. Also, cloning a + Transliterator object will now throw an + Error exception on failure to clone the internal + transliterator instead of resulting in a fatal error. + + + + In the LDAP extension, providing an unknown modification type to + ldap_batch_modify will now throw an + Error exception instead of resulting in a fatal error. + + + + In the mbstring extension, the mb_ereg and + mb_eregi functions will now throw a + ParseError exception if an invalid PHP expression is + provided and the 'e' option is used. + + + + In the Mcrypt extension, the mcrypt_encrypt and + mcrypt_decrypt will now throw an + Error exception instead of resulting in a fatal error + if mcrypt cannot be initialized. + + + + In the mysqli extension, attempting to read an invalid property or write to + a readonly property will now throw an Error exception + instead of resulting in a fatal error. + + + + In the Reflection extension, failing to retrieve a reflection object or + retrieve an object property will now throw an Error + exception instead of resulting in a fatal error. + + + + In the Session extension, custom session handlers that do not return strings + for session IDs will now throw an Error exception + instead of resulting in a fatal error when a function is called that must + generate a session ID. + + + + In the SimpleXML extension, creating an unnamed or duplicate attribute will + now throw an Error exception instead of resulting in + a fatal error. + + + + In the SPL extension, attempting to clone an + SplDirectory object will now throw an + Error exception instead of resulting in a fatal + error. Similarly, calling ArrayIterator::append when + iterating over an object will also now throw an Error + exception. + + + + In the standard extension, the assert function, when + provided with a string argument as its first parameter, will now throw a + ParseError exception instead of resulting in a + catchable fatal error if the PHP code is invalid. Similarly, calling + forward_static_call outside of a class scope will now + throw an Error exception. + + + + In the Tidy extension, creating a tidyNode manually + will now throw an Error exception instead of + resulting in a fatal error. + + + + In the WDDX extension, a circular reference when serializing will now throw + an Error exception instead of resulting in a fatal + error. + + + + In the XML-RPC extension, a circular reference when serializing will now + throw an instance of Error exception instead of + resulting in a fatal error. + + + + In the Zip extension, the ZipArchive::addGlob + method will now throw an Error exception instead of + resulting in a fatal error if glob support is not available. + + + + + Lexically bound variables cannot reuse names + + + Variables bound to a closure via + the use construct cannot use the same name as any + &link.superglobals;, $this, or any parameter. For + example, all of these function definition will result in a fatal error: + + + + + + + + + + + JSON encoding and decoding + + The serialize_precision ini setting now controls the + serialization precision when encoding doubles. + + + Decoding an empty key now results in an empty property name, rather than + _empty_ as a property name. + + + + 1]))); +]]> + + &example.outputs.similar; + + + int(1) +} +]]> + + + + + When supplying the JSON_UNESCAPED_UNICODE flag to + json_encode, the sequences U+2028 and U+2029 are now + escaped. + + + + + + Changes to <function>mb_ereg</function> and <function>mb_eregi</function> + parameter semantics + + + The third paramter to the mb_ereg and + mb_eregi functions (regs) will now be + set to an empty array if nothing was matched. Formely, the parameter would + not have been modified. + + + + + Drop support for the sslv2 stream + + The sslv2 stream has now been dropped in OpenSSL. + +