Re: Update of Coding standards line length

From: Date: Tue, 25 Nov 2008 04:09:22 +0000
Subject: Re: Update of Coding standards line length
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-51142@lists.php.net to get a copy of this message
I'm +1 for it ignoring it in tools like PHPCS in the following scenarios - Docblocks. If I find and replace a word and it pushes over a limit, I get a whole lot of warnings and its a PITA to touch up. - Stupidly long regexp. Sometimes, it's useful to have one huge line. - Raising errors using constants. PEAR::raiseError("Quite normal length message arghhhhh", PEAR_Namespace_Hacky_Classname::SOMETHING_FOO_MESSAGE_CODE_HERE); and PEAR::raiseError("Quite normal length message arghhhhh", PEAR_Namespace_Hacky_Classname::SOMETHING_FOO_MESSAGE_CODE_HERE); - Function declarations using default arguments and class constants function foo($bar = PEAR_Namespace_Hacky_Classname::SOMETHING_FOO_MESSAGE_CODE_HERE) { } I know there are other CS changes in the works to make some of these less of a PITA.

« previous php.pear.dev (#51142) next »