cvs: php4 / CODING_STANDARDS
| From: | Derick Rethans | Date: | Mon, 09 Sep 2002 07:54:12 +0000 |
| Subject: | cvs: php4 / CODING_STANDARDS | ||
| Groups: | php.cvs | ||
| Request: | Send a blank email to php-cvs+get-13957@lists.php.net to get a copy of this message | ||
derick Mon Sep 9 03:54:12 2002 EDT
Modified files:
/php4 CODING_STANDARDS
Log:
- spaces instead of tabs
Index: php4/CODING_STANDARDS
diff -u php4/CODING_STANDARDS:1.21 php4/CODING_STANDARDS:1.22
--- php4/CODING_STANDARDS:1.21 Mon Sep 9 03:52:39 2002
+++ php4/CODING_STANDARDS Mon Sep 9 03:54:11 2002
@@ -97,9 +97,9 @@
try avoiding it.
[7] Use PHP_* macros in the PHP source, and ZEND_* macros in the Zend
- part of the source. Although the PHP_* macro's are mostly aliased to the
- ZEND_* macros it gives a better understanding on what kind of macro you're
- calling.
+ part of the source. Although the PHP_* macro's are mostly aliased to the
+ ZEND_* macros it gives a better understanding on what kind of macro you're
+ calling.
[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.
@@ -200,13 +200,13 @@
[3] Be generous with whitespace and braces. Always prefer:
- if (foo) {
- bar;
- }
+ if (foo) {
+ bar;
+ }
- to:
+ to:
- if(foo)bar;
+ if(foo)bar;
Keep one empty line between the variable declaration section and
the statements in a block, as well as between logical statement