cvs: php4 / CODING_STANDARDS

From: Date: Thu, 14 Mar 2002 03:25:47 +0000
Subject: cvs: php4 / CODING_STANDARDS
Groups: php.cvs 
Request: Send a blank email to php-cvs+get-10090@lists.php.net to get a copy of this message
elixer Wed Mar 13 22:25:47 2002 EDT Modified files: /php4 CODING_STANDARDS Log: Translate to English. # I still don't know what a 'tag search' is... Index: php4/CODING_STANDARDS diff -u php4/CODING_STANDARDS:1.11 php4/CODING_STANDARDS:1.12 --- php4/CODING_STANDARDS:1.11 Wed Mar 13 21:17:22 2002 +++ php4/CODING_STANDARDS Wed Mar 13 22:25:46 2002 @@ -60,12 +60,12 @@ check its man page again, and only then, consider using it, and even then, try avoiding it. -[7] Use ZEND_* macro instead of PHP_* macro. Use of PHP_* macros are - not recommended. Since most of PHP_* macros are ZEND_* macro alias, use of - PHP_* macro makes browsing source with tag search harder. +[7] Use ZEND_* macros instead of PHP_* macros. Use of PHP_* macros is not + recommended. Since most of the PHP_* macros are ZEND_* macro aliases, using + the PHP_* macros makes browsing the source code with a tag search harder. -[8] Use assert(). assert.h is included in php.h if it is available. - Not only good assertion catch bugs, but also it makes easier to read code. +[8] Use assert(). assert.h is included in php.h if it is available. Not only + does good assertion catch bugs, but it also helps with code readability. Naming Conventions ------------------

« previous php.cvs (#10090) next »