sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Minor update to the migration 5.4 guide, mostly slight rewording

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@323719 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Philip Olson 2012-03-01 17:28:30 +00:00
parent c272030e25
commit 6129495ac9
1 changed files with 34 additions and 36 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

70
appendices/migration54.xml
View file

@ -72,18 +72,18 @@
<simpara>
<link linkend="features.safe-mode">Safe mode</link> is no
longer supported. Any applications that rely on safe mode may need
adjustements in terms of security.
adjustmentubg, in terms of security.
</simpara>
</listitem>
<listitem>
<simpara>
<link linkend="security.magicquotes">Magic quotes</link> has been removed. Applications relying
on this feature need to be updated to avoid security issues.
on this feature may need to be updated, to avoid security issues.
</simpara>
<simpara>
<function>get_magic_quotes_gpc</function> and <function>get_magic_quotes_runtime</function>
now always return &false;. <function>set_magic_quotes_runtime</function> raises an
<constant>E_CORE_ERROR</constant>.
<constant>E_CORE_ERROR</constant> level error.
</simpara>
</listitem>
<listitem>
@ -102,17 +102,16 @@
<simpara>
The <link linkend="control-structures.break">break</link>
and <link linkend="control-structures.continue">continue</link>
statements don't accept variable arguments anymore, i.e. writing
<literal>break 1 + foo() * $bar;</literal> is not possible. You can obviously still use
static arguments, like <literal>break 2;</literal>.
statements no longer accept variable arguments (e.g., <literal>break 1 + foo() * $bar;</literal>).
Static arguments still work, such as <literal>break 2;</literal>.
</simpara>
</listitem>
<listitem>
<simpara>
In the <link linkend="book.datetime">date and time extension</link> the timezone can no longer be
In the <link linkend="book.datetime">date and time extension</link>, the timezone can no longer be
set using the TZ environment variable. Instead you have to specify a timezone using the
<link linkend="ini.date.timezone">date.timezone</link> ini option or the <function>date_default_timezone_set</function>
function. PHP will no longer try to guess the used timezone and instead fall back to "UTC" and issue
<link linkend="ini.date.timezone">date.timezone</link> ini option or <function>date_default_timezone_set</function>
function. PHP will no longer attempt to guess the timezone, and will instead fall back to "UTC" and issue
a warning.
</simpara>
</listitem>
@ -123,24 +122,24 @@
if you try to use them. Offsets of types double, bool and null produce a notice. Numeric strings
(e.g. <literal>$a['2']</literal>) still work as before. Note that offsets like <literal>'12.3'</literal>
and <literal>'5 foobar'</literal> are considered non-numeric and produce a warning, but are converted
to 12 and 5 respectively for BC reasons.
to 12 and 5 respectively, for backward compatibility reasons.
</simpara>
</listitem>
<listitem>
<simpara>
Converting an array to string will now cause an <constant>E_NOTICE</constant>. The result of
the cast will still be <literal>"Array"</literal>.
Converting an array to string will now generate an <constant>E_NOTICE</constant> level
error, and the result of the cast will still be the string <literal>"Array"</literal>.
</simpara>
</listitem>
<listitem>
<simpara>
Turning &null;, &false; or an empty string into an object by adding a property
will now emit a warning instead of an <constant>E_STRICT</constant> error.
Turning &null;, &false;, or an empty string into an object by adding a property
will now emit a <constant>E_WARNING</constant> level instead of <constant>E_STRICT</constant>.
</simpara>
</listitem>
<listitem>
<simpara>
Parameter names that shadow superglobals now cause a fatal error. This prohibits code like
Parameter names that shadow super globals now cause a fatal error. This prohibits code like
<literal>function foo($_GET, $_POST) {}</literal>.
</simpara>
</listitem>
@ -157,15 +156,16 @@
</listitem>
<listitem>
<simpara>
<function>htmlentities</function> now emits an <constant>E_STRICT</constant> warning when used with
asian character sets, as in that case <function>htmlentities</function> has (and already had before
this version) the same functionality as <function>htmlspecialchars</function>.
If you use <function>htmlentities</function> with asian character sets, it
works like <function>htmlspecialchars</function> - this has always been the
case in previous versions of PHP, but now an <constant>E_STRICT</constant>
level error is emitted
</simpara>
</listitem>
</itemizedlist>
<simpara>
The following keyword(s) are now reserved and may not be used in function,
class, etc. names.
The following keywords are now <link linkend="reserved">reserved</link>, and may not be used
as names by functions, classes, etc.
</simpara>
<itemizedlist>
<listitem>
@ -317,7 +317,8 @@
</listitem>
<listitem>
<simpara>
PHP-FPM: Added <literal>process.max</literal> setting to control the number of process FPM can fork
PHP-FPM: Added the <literal>process.max</literal> setting, to control the number
of processes that FPM can fork.
</simpara>
</listitem>
</itemizedlist>
@ -388,14 +389,8 @@
<itemizedlist>
<listitem>
<simpara>
Added optional argument to <function>debug_backtrace</function> and
<function>debug_print_backtrace</function> to limit the amount of stack frames returned
</simpara>
</listitem>
<listitem>
<simpara>
<function>is_a</function> and <function>is_subclass_of</function> now have third
boolean parameter, which specifies if the first argument can be a string class name.
Added the optional <parameter>limit</parameter> parameter to <function>debug_backtrace</function>
and <function>debug_print_backtrace</function>, to limit the amount of stack frames returned.
</simpara>
</listitem>
</itemizedlist>
@ -403,7 +398,8 @@
<itemizedlist>
<listitem>
<simpara>
Added no padding option to <function>openssl_encrypt</function> and <function>openssl_decrypt</function>
Added a no padding option to the <function>openssl_encrypt</function> and <function>openssl_decrypt</function>
functions.
</simpara>
</listitem>
</itemizedlist>
@ -683,7 +679,7 @@
</itemizedlist>
<simpara>
Changes in extension behaviour, and new features:
Changes in extension behavior, and new features:
</simpara>
<itemizedlist>
<listitem>
@ -1332,13 +1328,15 @@
Added support for storing upload progress feedback in session data.
</simpara>
<simpara>
Changed session.entropy_file to default to /dev/urandom or /dev/arandom if
either is present at compile time.
Changed <link linkend="ini.session.entropy-file">session.entropy_file</link>, which
now defaults to <literal>/dev/urandom</literal> or <literal>/dev/arandom</literal> if
either are present at compile time.
</simpara>
</listitem>
<listitem>
<simpara>
<constant>E_ALL</constant> now includes <constant>E_STRICT</constant>.
<constant>E_ALL</constant> now includes <constant>E_STRICT</constant> level
errors, as per the <link linkend="ini.error-reporting">error_reporting</link>.
</simpara>
</listitem>
<listitem>
@ -1346,8 +1344,8 @@
<link linkend="book.snmp">SNMP</link> now has an OOP API.
</simpara>
<simpara>
Functions now return FALSE on every error condition including SNMP-related
(no such instance, end of MIB, etc). Thus, in patricular, breaks previous behaviour
Functions now return &false; on every error condition including SNMP-related
(no such instance, end of MIB, etc). Thus, in particular, breaks previous behavior
of get/walk functions returning an empty string on SNMP-related errors.
</simpara>
<simpara>