RE: [PEAR-QA] CS discussion
| From: | Lukas Smith | Date: | Thu, 17 Jul 2003 15:18:47 +0000 |
| Subject: | RE: [PEAR-QA] CS discussion | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-70@lists.php.net to get a copy of this message | ||
> From: Jon Parise [mailto:jon@php.net]
> On Wed, Jul 16, 2003 at 10:13:09AM +0100, Bruno Pedro wrote:
>
> > I also prefer that solution (I suggested that in the first place),
but
> > after taking a look at the Java Coding Standard Version 2.0 "Line
> > length" section I came across this:
>
> [snipped]
>
> It's not hard to find examples of either style in coding standards:
>
> Christopher Seiwald advocates breaking conditions at the operators and
> then aligning them:
>
> http://www.perforce.com/perforce/papers/prettycode.html
>
> The Python style guides suggests wrapping lines after the operator:
>
> http://www.python.org/peps/pep-0007.html (C code)
> http://www.python.org/peps/pep-0008.html (Python code)
To conclude:
There is not an obvious choice.
CS stuff doesn't need to be obvious. It is more about deciding if
something should be regulated or not and if yes choosing one of the
fairly random choices.
So is this something that should be regulated or not?
I think it would be a good idea.
Then its just upto someone (probably the yet to be announced PEAR Group
as was decided at the PEAR meeting) to make a choice in between all the
possible options.
Regards,
Lukas