summaryrefslogtreecommitdiff
path: root/CODING_STANDARDS
diff options
context:
space:
mode:
authorYasuo Ohgaki <yohgaki@php.net>2002-09-08 22:38:57 (GMT)
committerYasuo Ohgaki <yohgaki@php.net>2002-09-08 22:38:57 (GMT)
commitab0da7dc334cb6d44d0d5571f97f1c723bf1c61a (patch)
tree2b898803c44c32aadfff50136a579fa526468bb3 /CODING_STANDARDS
parentcbf5e3ca0625fbd3a719d90f81ead2ed62ba52d2 (diff)
downloadphp-ab0da7dc334cb6d44d0d5571f97f1c723bf1c61a.tar.gz
It seems we're better to mention about missing functions.
PHP_FUNCTION -> ZEND_FUNCTION
Diffstat (limited to 'CODING_STANDARDS')
-rw-r--r--CODING_STANDARDS8
1 files changed, 6 insertions, 2 deletions
diff --git a/CODING_STANDARDS b/CODING_STANDARDS
index 596465f..d50e35c 100644
--- a/CODING_STANDARDS
+++ b/CODING_STANDARDS
@@ -115,11 +115,15 @@ Exceptions:
cvs user foo. This allows easier tracking of why code was commented out,
especially in bundled libraries.
+[10] Do no define that is not available. For instance, if library available is
+ missing function(s), do not define function nor raise error for missing
+ function(s).
+
Naming Conventions
------------------
[1] Function names for user-level functions should be enclosed with in
- the PHP_FUNCTION() macro. They should be in lowercase, with words
+ the ZEND_FUNCTION() macro. They should be in lowercase, with words
underscore delimited, with care taken to minimize the letter count.
Abbreviations should not be used when they greatly decrease the
readability of the function name itself.
@@ -220,7 +224,7 @@ function does. It would look like this:
/* {{{ proto int abs(int number)
Returns the absolute value of the number */
-PHP_FUNCTION(abs)
+ZEND_FUNCTION(abs)
{
...
}