Egon:
> I would see a space. The formatted function prototypes have already a
> space between function name and opening parenthesis. With the space the
> code is more readable.
The first can be changed, though I can come into your second point:
better readable. In the case of a prototype, I must
Damien Seguy writes:
> on 8/08/01 18:32, Hojtsy Gabor at [EMAIL PROTECTED] wrote:
>
> >>> Right now, here is the situation :
> >>> no space : +2
> >>> space: 0
> Latest update :
>
> Right now, here is the situation :
> no space : +3
> space: +1
>
>
> Anyone else want to state about th
on 8/08/01 18:32, Hojtsy Gabor at [EMAIL PROTECTED] wrote:
>>> Right now, here is the situation :
>>> no space : +2
>>> space: 0
Latest update :
Right now, here is the situation :
no space : +3
space: +1
Anyone else want to state about this?
let's keep the polls open, this is vacation
> > Right now, here is the situation :
> > no space : +2
> > space: 0
>
> I would see a space. The formatted function prototypes have already a
> space between function name and opening parenthesis. With the space the
> code is more readable.
>
> -1 (space)
We should write codes according t
On Wed, Aug 08, 2001 at 09:51:50AM +0200, Damien Seguy wrote:
> on 8/08/01 0:06, Jeroen van Wolffelaar at [EMAIL PROTECTED] wrote:
>
> > From PEAR coding standards (function calls):
> I got those one from README file in phpdoc/README.
>
> I do agree with the no space between function name and o
on 8/08/01 0:06, Jeroen van Wolffelaar at [EMAIL PROTECTED] wrote:
> From PEAR coding standards (function calls):
I got those one from README file in phpdoc/README.
I do agree with the no space between function name and opening parenthesis.
At least, we should be coherent with the rest of the P
> MMM, I thought that whitespace between funcname and open parenthesis was
> standard guideline for docs.
>
> README :
> 8. If an example of using arguments specific to a newer version of
>php, it is helpful to note that in the example:
>
>foo_function_exec ("bar", "baz"); // s
