From d9cee3fbb32a45988ca92e2f10f91774a8935e4d Mon Sep 17 00:00:00 2001 From: Damien Seguy Date: Wed, 19 May 2004 14:11:51 +0000 Subject: [PATCH] adding cosmetics tags git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@159013 c90b9560-bf6c-de11-be94-00142212c4b1 --- appendices/about.xml | 10 ++++---- appendices/debugger.xml | 6 ++--- appendices/history.xml | 4 ++-- appendices/migration4.xml | 7 +++--- appendices/phpdevel.xml | 49 ++++++++++++++++++++------------------- 5 files changed, 40 insertions(+), 36 deletions(-) diff --git a/appendices/about.xml b/appendices/about.xml index 9711d6d35c..73acd8242d 100644 --- a/appendices/about.xml +++ b/appendices/about.xml @@ -1,5 +1,5 @@ - + + Debugging PHP @@ -78,11 +78,11 @@ A line has this format: - + - + diff --git a/appendices/history.xml b/appendices/history.xml index 3383b0e753..637a12ba3e 100644 --- a/appendices/history.xml +++ b/appendices/history.xml @@ -1,5 +1,5 @@ - + History of PHP and related projects @@ -313,7 +313,7 @@ Articles about PHP appeared in Dr. Dobbs, Linux Enterprise, Linux Magazine and many more. Articles about migrating ASP-based - applications to PHP under Windows even appear on Microsoft's + applications to PHP under Windows even appear on Microsoft's very own MSDN! diff --git a/appendices/migration4.xml b/appendices/migration4.xml index d47918a2cd..df554337b4 100644 --- a/appendices/migration4.xml +++ b/appendices/migration4.xml @@ -1,5 +1,5 @@ - + Migrating from PHP 3 to PHP 4 @@ -460,8 +460,9 @@ php_admin_flag [PHP directive name] [On|Off] While handling of global variables had the focus on to be easy in PHP 3 and early versions of PHP 4, the focus has changed to be more secure. While in PHP 3 the following example worked fine, in PHP 4 it - has to be unset($GLOBALS["id"]);. This is only one issue of global - variable handling. You should always have used $GLOBALS, with + has to be unset(unset($GLOBALS["id"]));. This is + only one issue of global + variable handling. You should always have used $GLOBALS, with newer versions of PHP 4 you are forced to do so in most cases. Read more on this subject in the global references section. diff --git a/appendices/phpdevel.xml b/appendices/phpdevel.xml index 234fdc8b5c..5be4219952 100644 --- a/appendices/phpdevel.xml +++ b/appendices/phpdevel.xml @@ -1,5 +1,5 @@ - + Extending PHP 3 @@ -60,7 +60,8 @@ if (ARG_COUNT(ht) != 2 || getParameters(ht,2,&arg1,&arg2)==FAILURE) { sent by reference or by value, you can either start over with the parameter by calling pval_destructor on it, or if it's an ARRAY you want to add to, you can use functions similar to the ones in - internal_functions.h which manipulate return_value as an ARRAY. + internal_functions.h which manipulate return_value as an ARRAY. + Also if you change a parameter to IS_STRING make sure you first @@ -240,7 +241,7 @@ convert_string_to_number(arg1); /* Converts string to either LONG or DOUBLE dep - Checking whether $foo exists in a symbol table + Checking whether <varname>$foo</varname> exists in a symbol table - This code declares a new array, named $foo, in the active symbol + This code declares a new array, named $foo, in the active symbol table. This array is empty. @@ -326,7 +327,7 @@ hash_next_index_insert(arr.value.ht,&entry,sizeof(pval),NULL); hash_next_index_insert() uses more or less the same logic as - "$foo[] = bar;" in PHP 2.0. + $foo[] = bar; in PHP 2.0. If you are building an array to return from a function, you can @@ -794,7 +795,7 @@ php3_list_delete(resource_id->value.lval); - E_NOTICE + <constant>E_NOTICE</constant> Notices are not printed by default, and indicate that the script encountered something that could indicate an error, but could also @@ -805,7 +806,7 @@ php3_list_delete(resource_id->value.lval); - E_WARNING + <constant>E_WARNING</constant> Warnings are printed by default, but do not interrupt script execution. These indicate a problem that should have been trapped @@ -815,7 +816,7 @@ php3_list_delete(resource_id->value.lval); - E_ERROR + <constant>E_ERROR</constant> Errors are also printed by default, and execution of the script is halted after the function returns. These indicate errors that can @@ -824,7 +825,7 @@ php3_list_delete(resource_id->value.lval); - E_PARSE + <constant>E_PARSE</constant> Parse errors should only be generated by the parser. The code is listed here only for the sake of completeness. @@ -832,66 +833,66 @@ php3_list_delete(resource_id->value.lval); - E_CORE_ERROR + <constant>E_CORE_ERROR</constant> - This is like an E_ERROR, except it is generated by the core + This is like an E_ERROR, except it is generated by the core of PHP. Functions should not generate this type of error. - E_CORE_WARNING + <constant>E_CORE_WARNING</constant> - This is like an E_WARNING, except it is generated by the core + This is like an E_WARNING, except it is generated by the core of PHP. Functions should not generate this type of error. - E_COMPILE_ERROR + <constant>E_COMPILE_ERROR</constant> - This is like an E_ERROR, except it is generated by the Zend Scripting + This is like an E_ERROR, except it is generated by the Zend Scripting Engine. Functions should not generate this type of error. - E_COMPILE_WARNING + <constant>E_COMPILE_WARNING</constant> - This is like an E_WARNING, except it is generated by the Zend Scripting + This is like an E_WARNING, except it is generated by the Zend Scripting Engine. Functions should not generate this type of error. - E_USER_ERROR + <constant>E_USER_ERROR</constant> - This is like an E_ERROR, except it is generated in PHP code by using + This is like an E_ERROR, except it is generated in PHP code by using the PHP function trigger_error. Functions should not generate this type of error. - E_USER_WARNING + <constant>E_USER_WARNING</constant> - This is like an E_WARNING, except it is generated by using the PHP + This is like an E_WARNING, except it is generated by using the PHP function trigger_error. Functions should not generate this type of error. - E_USER_NOTICE + <constant>E_USER_NOTICE</constant> - This is like an E_NOTICE, except it is generated by using the PHP + This is like an E_NOTICE, except it is generated by using the PHP function trigger_error. Functions should not generate this type of error. - E_ALL + <constant>E_ALL</constant> All of the above. Using this error_reporting level will show all error types.