[PEPr] Comment on RFC::Coding standard enhancements
| From: | Dan Scott | Date: | Mon, 03 Nov 2008 15:45:29 +0000 |
| Subject: | [PEPr] Comment on RFC::Coding standard enhancements | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-51006@lists.php.net to get a copy of this message | ||
Dan Scott (http://pear.php.net/user/dbs) has commented on the proposal for RFC::Coding standard
enhancements.
Comment:
Daniel's comments on all 3 issues look like they were written after running
phpcs against my code (242 errors, 142 warnings) - very familiar.
I would be a big +1 to at least relaxing the level of enforcement on these
things to "warning" rather than "error". It was irritating to spend about
an hour cleaning up the "errors" in File_MARC that made no visible
difference to the documentation (okay - there were a handful of incorrect
parameter names in the docblocks that were valuable and rightfully called
errors) or to the quality of the code.
I'm concerned that enforcing the coding standards for whitespace at the
level of "error" will push potential PEAR developers away. We tend to have
a whole lot of other things to do; reformatting code is a pretty low
priority.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=538
--
Sent by PEPr, the automatic proposal system at http://pear.php.net