From: "Gabor Hojtsy" <[EMAIL PROTECTED]>
> > > > Therefore I thought this way of writing the protos is ok.
> > > > One says care for the pear standards, others say do not.
> > > > So how should this be done in the future?
> > >
> > > There must be some standard, we should not let alone all
> > > writers IMHO, to write things in their own preference.
> > > We have the 4 space rule, and other things. Previously
> > > we agreed (??) to use the PEAR standard. There were not
> > > too much talk about this...
> >
> > I know myself many writers personally :) There haven´ t been not
so
> > much talk about this problem because I have not so much free
time as
> > you. The PHP documentation doesn´ t use the so called PEAR
standard.
> > It is only you who want this change. Please see it in a real
world.
> > We cannot change the PHP manuals, if someone make a commit into
the
> > documentation rules.
>
> As you can see in the commit history, it was _not_ me, who added
> that "convention". But I think it is useful to have one standard.
> It eases the reading of the manual. There is one standard
> developed by PHP developers, the PEAR standard. I don't say we
> _need to_ force everybody to use this. I say it would be good
> to have any common standard for the PHP codes in the manual,
including
> how we present sample outputs, and the like... This not only
> eases the reading, but also eases the writing, as someone need
> not ask about how this should be written (as happened in the
> past - this was because this thread was started), because it
> is written down. Converting all the documentation examples is
> of course not a days work, but we can switch to use one
> standard slowly step by step, while upgrading the examples,
> and descriptions.
I should know the history. The PEAR standard was written some years
after the PHP manual. So I don´t see any improvement if writers
should write
function_name(args)
{
// do something
}
instead of
function_name (args) {
// do something
}
-Egon
