Re: QA: Package coding standards check
| From: | Chuck Burgess | Date: | Thu, 24 Jan 2008 04:05:58 +0000 |
| Subject: | Re: QA: Package coding standards check | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-48987@lists.php.net to get a copy of this message | ||
I'd prefer this did become part of the CS, and therefore into PHPCS's PEAR
standard.
CRB
On Jan 23, 2008 5:31 PM, Christian Schmidt <pear.php.net@chsc.dk> wrote:
> Is there general consensus that newlines should be permitted after the
> opening parenthesis of a function call, like this?
>
>
> $this->thisIsIsAVeryLongMethodNameThatDoesNotLeaveMuchRoomForTheParameters(
> $longVariableName, $evenLongerVariableName);
>
> If so, I'll open a bug for this.
>
>
> Christian
>
>
> David Sanders wrote:
> > whoever drew up the coding standards must've forgotten to put the "no
> > space except for newlines" clause in there somewhere.
> >
> > i prefer igor's method ;)
> >
> > Chuck Burgess wrote:
> >> On 10/22/07, Igor Feghali <igor.feghali@gmail.com> wrote:
> >>> <?php
> >>> $result = $this->dumpSequence(
> >>> $database_definition['sequences'][$sequence],
> >>> $sequence, $eol, $dump
> >>> );
> >>> ?>
> >>>
> >>> gives me the errors:
> >>> error 458 Space after opening parenthesis of function call
> >>> prohibited
> >>> error 461 Space before closing parenthesis of function call
> >>> prohibited
> >>>
> >>> I can't keep the lines behind the 85 character limit if I am not
> allowed
> >>> to break the functions arguments.
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
CRB