the following only deals with a minor formatting issue, which nevertheless disturbs me for quite a while.
I suggest changing the method synopsis formatting in the docs from (example; note the whitespace around the first parenthesis):
mixed array_search ( mixed needle, array haystack [, bool strict])
to some PEAR coding standards conform:
(1) mixed array_search(mixed needle, array haystack [, bool strict])
or a maybe better readable:
(2) mixed array_search (mixed needle, array haystack [, bool strict])
I'd still prefer the first proposal. Opinions? Please comment, I won't commit this without some backing as it will change the overall look of php.net/manual. Below my current cvs diff which (hopefully) implements (1); did I miss something?
Since the type names and the optional [] signs are not used in the PHP syntax anyway, I don't think that this is really something to make in line with the PEAR coding standards. AFAIS it is more readable to have some spaces between the function name and the first param's type name. Have you noticed that you have not removed the space before [, although it would be desired to be in line with the PEAR coding standards. The reason? Readability. There are no $ signs in these protos to help readbility.
Goba
