Re: PHP_CodeSniffer as part of the pepr proposal process
| From: | Greg Sherwood | Date: | Sun, 06 May 2007 22:21:11 +0000 |
| Subject: | Re: PHP_CodeSniffer as part of the pepr proposal process | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-46651@lists.php.net to get a copy of this message | ||
Gregory Beaver wrote:
I would be interested in investigating setting up codesniffer as a cron job for checking PEPr proposals. I'm assuming it would time out if used to check a large proposal. Have you tried it on something vast like phpDocumentor? I just got a new version of phpDocumentor from PEAR, but all the newlines are /r/n, which causes a significant amount of errors, That might be an issue in itself for PEAR.I'll get rid of those errors and give it a run when I get time. First impressions are that PHP_CodeSniffer doesn't like some of the code, so I'll look into why and fix any errors I find. PHP_CodeSniffer has been tested on PHP5 code much more than PHP4, so it's possible that it's looking for a keyword somewhere that doesn't exist. If anyone has the time to run PHP_CodeSniffer on your own package, please let me know any issues you find. Thanks to all the PEAR devs who have already submitted reports. Greg