mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 00:48:54 +00:00
Remove few "you"s
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@236231 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
f09c05c447
commit
55db3afa9b
1 changed files with 9 additions and 9 deletions
|
@ -1,5 +1,5 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.22 $ -->
|
||||
<!-- $Revision: 1.23 $ -->
|
||||
<appendix id="migration52">
|
||||
<title>Migrating from PHP 5.1.x to PHP 5.2.x</title>
|
||||
|
||||
|
@ -1894,7 +1894,7 @@ $obj->getCommentName('');
|
|||
<title>Error Reporting</title>
|
||||
<para>
|
||||
Some of the existing <constant>E_ERROR</constant> conditions have been
|
||||
converted to something that you can catch with a user-defined error
|
||||
converted to something that can be caught with a user-defined error
|
||||
handler. If an <link
|
||||
linkend="errorfunc.constants"><constant>E_RECOVERABLE_ERROR</constant></link>
|
||||
is not handled, it will behave in the same way as
|
||||
|
@ -1906,20 +1906,20 @@ $obj->getCommentName('');
|
|||
<link linkend="ini.error-reporting">error_reporting</link> constant is
|
||||
now 6143, where the previous value was 2047. Because PHP constants have
|
||||
no meaning outside of PHP, in some cases the integer value is used
|
||||
instead so these will need to be adjusted. So for example if you are
|
||||
instead so these will need to be adjusted. So for example by
|
||||
setting the error_reporting mode from either the
|
||||
<link linkend="apache.configuration">httpd.conf</link> or the
|
||||
<filename>.htaccess</filename> files, you will need to adjust the value
|
||||
accordingly. The same applies if you use the numeric value rather than the
|
||||
constant in your PHP scripts.
|
||||
<filename>.htaccess</filename> files, the value has to be changed
|
||||
accordingly. The same applies when the numeric values are used
|
||||
rather than the constants in PHP scripts.
|
||||
</para>
|
||||
<para>
|
||||
As a side-effect of a change made to prevent duplicate error messages when
|
||||
<link linkend="ini.track-errors">track_errors</link> is
|
||||
<literal>On</literal>, it is now necessary to return &false; from your
|
||||
error handler in order to populate
|
||||
<literal>On</literal>, it is now necessary to return &false; from
|
||||
user defined error handlers in order to populate
|
||||
<link linkend="reserved.variables.phperrormsg">$php_errormsg</link>. This
|
||||
provides you fine-grain control over the levels of messages stored.
|
||||
provides a fine-grain control over the levels of messages stored.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
|
|
Loading…
Reference in a new issue