From 64b0d7edbab19536d098a0a81e463a3238b38dd4 Mon Sep 17 00:00:00 2001 From: Richard Quadling Date: Wed, 11 Jul 2007 08:38:48 +0000 Subject: [PATCH] Updated migration4 - thank you Simion Onea. git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@239467 c90b9560-bf6c-de11-be94-00142212c4b1 --- appendices/migration4.xml | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/appendices/migration4.xml b/appendices/migration4.xml index 8a6383a41f..b41bec2603 100644 --- a/appendices/migration4.xml +++ b/appendices/migration4.xml @@ -1,5 +1,5 @@ - + Migrating from PHP 3 to PHP 4 @@ -132,8 +132,8 @@ php_admin_flag [PHP directive name] [On|Off] type lines! You have to convert these yourself. - To convert your Apache configuration files, run the apconf-conv.sh - script (available in the scripts/apache/ directory). For example: + To convert your Apache configuration files, run the apconf-conv.sh + script (available in the scripts/apache/ directory). For example: Likewise, your old &htaccess; files will be saved with - an .orig prefix. + an .orig suffix. - The conversion scripts require awk to be installed. + The conversion scripts require 'awk' to be installed. @@ -187,7 +187,7 @@ php_admin_flag [PHP directive name] [On|Off] a different file. - It still perfectly legal to include additional code within loops + It is still perfectly legal to include additional code within loops or other control structures, only the controlling keywords and corresponding curly braces {...} have to be within the same compile unit (file or evaled @@ -241,7 +241,7 @@ php_admin_flag [PHP directive name] [On|Off] When upgrading code or servers from PHP 3 to PHP 4 you should check these settings and calls to error_reporting or you might disable - reporting the new error types, especially E_COMPILE_ERROR. This + reporting the new error types, especially E_COMPILE_ERROR. This may lead to empty documents without any feedback of what happened or where to look for the problem. @@ -257,7 +257,7 @@ php_admin_flag [PHP directive name] [On|Off] This has lead to a lot of unreproducible bug reports in the past where people reported script engine problems they were not - capable to track down while the &true; case was usually some + capable to track down while the true case was usually some missing '}' in a required file that the parser was not able to report due to a misconfigured error reporting system. @@ -278,8 +278,8 @@ php_admin_flag [PHP directive name] [On|Off] the intended thing now, could easily be broken by changes in other places. PHP 4 will output a lot of notice messages in such situations where PHP 3 didn't. The easy fix is to just - turn off E_NOTICE messages, but it is usually a good idea to fix - the code instead. + turn off E_NOTICE messages, but it is usually + a good idea to fix the code instead. The most common case that will now produce notice messages is the @@ -324,8 +324,8 @@ php_admin_flag [PHP directive name] [On|Off]
<literal>empty("0")</literal> - The perhaps most controversial change in behavior has happened to the - behavior of the empty. A String containing + Perhaps the most controversial change in behavior has happened to + empty. A String containing only the character '0' (zero) is now considered empty while it wasn't in PHP 3. @@ -361,7 +361,7 @@ php_admin_flag [PHP directive name] [On|Off] possible to change the behavior of the parser (now embedded in the Zend engine) at runtime as parsing already happened by then. So the function short_tags no longer - exists. You can still change the parsers behavior by setting + exists. You can still change the parser's behavior by setting appropriate values in the &php.ini; file.