>> But what about arrays? Can we discuss Pear guys about that? > > I don't mind that much for arrays, but it *is* a language construct, and > from what I read from the CS that means that there should be a space > there.
"Control statements should have one space between the control keyword and opening parenthesis, to distinguish them from function calls." As Goba said: Control statements != (fully) language constructs. Control statements (structures) are: if, else, elseif, while, do..while, for, foreach, break, continue, switch, declare, return, include(), require(), include_once() and require_once(). Array isn't there, it's not a control structure, just a language construct. Array doesn't controls the flaw of the processnig php codelines. Pear documentation talking about only control statements. Array is closer than internal functions than control structures, but it's not a real function, only a language construct. It's a good idea to distinguish between for () and mysql_connect(). It's clears that for isn't a function or something like. So, my reasons on use array as function: - It's _not_ a control structure, and Pear docs talked about them. - Full Pear code uses array as functions. I think the people who made Pear, and who declares Pear CS are the same, and they know what they do. - I think it's more important to distinguish between array and control statements than between array and functions. Cece -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
