Re: cvs: phpdoc /en/reference/array/functions array-combine.xml array-count-values.xml array-diff-assoc.xml array-diff.xml array-filter.xml
array-flip.xml array-intersect-assoc.xml array-int
| From: | Gabor Hojtsy | Date: | Sun, 17 Aug 2003 12:53:50 +0000 |
| Subject: | Re: cvs: phpdoc /en/reference/array/functions array-combine.xml array-count-values.xml array-diff-assoc.xml array-diff.xml array-filter.xml array-flip.xml array-intersect-assoc.xml array-int |
||
| References: | 1 2 3 4 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969355870@lists.php.net to get a copy of this message | ||
As far as I interpret PEAR CS, you add space between control structures and parentheses, eg. "if (", but not between other constructs, like "echo(". There is no statement on function looking non-functions in PEAR CS. So as far as PEAR CS goes, control structure and function call formats are defined, and they treat constucts as function in their own code. Consolusion: from my view Cece was right, and I do the same indenting in my code. GobaIt's still wrong :) array and return are not functions, they might look like them, but they aren't. The whole point of not using a space between functionname and parameters, and using a space with constructs is that you then can easily seperate them.actually, array and return are language constructs, so they should have the space, like:array ('foo');That elements are lang.contructs, but looks like as functions. So, i checked PEAR codes. All PEAR codes (including class Pear in PEAR.php) handles array() as functions, without spaces before opening bracket.