cvs: php4 / CODING_STANDARDS
| From: | Dan Kalowsky | Date: | Tue, 13 Aug 2002 21:44:59 +0000 |
| Subject: | cvs: php4 / CODING_STANDARDS | ||
| Groups: | php.cvs | ||
| Request: | Send a blank email to php-cvs+get-13331@lists.php.net to get a copy of this message | ||
kalowsky Tue Aug 13 17:44:59 2002 EDT
Modified files:
/php4 CODING_STANDARDS
Log:
As per the suggestion on php-dev, now please #ifdef 0_<username here>
Index: php4/CODING_STANDARDS
diff -u php4/CODING_STANDARDS:1.16 php4/CODING_STANDARDS:1.17
--- php4/CODING_STANDARDS:1.16 Tue Aug 13 16:55:42 2002
+++ php4/CODING_STANDARDS Tue Aug 13 17:44:59 2002
@@ -110,6 +110,11 @@
Function calls in assert conditions may also cause this problem, if
they modify one of their arguments or global variables.
+[9] When commenting out code using a #if statement, do NOT use 0 only. Append
+ to any 0 an _<cvs username here>. For example, #if 0_FOO, where FOO is
+ cvs user foo. This allows easier tracking of why code was commented out,
+ especially in bundled libraries.
+
Naming Conventions
------------------