Prev: This is a BUG
Next: HTML_QuickForms2
From: Laurent Laville on 7 Jul 2009 02:20
PEAR Announce a �crit :
> The new PEAR package PHP_CodeSniffer-1.2.0RC3 (beta) has been released at http://pear.php.net/.
>
> Release notes
> -------------
> - You can now use @codingStandardsIgnoreStart and @...End comments to suppress error messages (feature request #14002)
> - A warning is now included for files without any code when short_open_tag is set to Off (feature request #12952)
> - You can now use relative paths to your custom standards with the --standard cmd line arg (feature request #14967)
> - You can now override magic methods and functions in PEAR ValidFunctionNameSniff (feature request #15830)
> - MySource IncludeSystemSniff now recognises widget action classes
> - MySource IncludeSystemSniff now knows about unit test classes and changes rules accordingly
>


*What's wrong with PHPCS 1.2.0RC3 ?*

I've just upgraded from 1.2.0RC2, and run it on many package and got
tone of errors and warnings.

Here are examples
1. ===>

PHP CODE SNIFFER REPORT SUMMARY
--------------------------------------------------------------------------------

FILE ERRORS
WARNINGS

--------------------------------------------------------------------------------

C:\wamp\bin\php\php5.2.9-2\PEAR\HTML\CSS.php 2179 171
--------------------------------------------------------------------------------

A TOTAL OF 2179 ERROR(S) AND 171 WARNING(S) WERE FOUND IN 1 FILE(S)
--------------------------------------------------------------------------------

2. ===>

PHP CODE SNIFFER REPORT SUMMARY
--------------------------------------------------------------------------------

FILE ERRORS
WARNINGS

--------------------------------------------------------------------------------

C:\wamp\bin\php\php5.2.9-2\PEAR\HTTP\Request2.php 946 151
--------------------------------------------------------------------------------

A TOTAL OF 946 ERROR(S) AND 151 WARNING(S) WERE FOUND IN 1 FILE(S)
--------------------------------------------------------------------------------

*While with PHPCS 1.2.0RC2 I got only*

1. ===>

PHP CODE SNIFFER REPORT SUMMARY
--------------------------------------------------------------------------------

FILE ERRORS
WARNINGS

--------------------------------------------------------------------------------

C:\wamp\bin\php\php5.2.9-2\PEAR\HTML\CSS.php 1 0
--------------------------------------------------------------------------------

A TOTAL OF 1 ERROR(S) AND 0 WARNING(S) WERE FOUND IN 1 FILE(S)
--------------------------------------------------------------------------------


2. ===>

PHP CODE SNIFFER REPORT SUMMARY
--------------------------------------------------------------------------------

FILE ERRORS
WARNINGS

--------------------------------------------------------------------------------

C:\wamp\bin\php\php5.2.9-2\PEAR\HTTP\Request2.php 165 22
--------------------------------------------------------------------------------

A TOTAL OF 165 ERROR(S) AND 22 WARNING(S) WERE FOUND IN 1 FILE(S)
--------------------------------------------------------------------------------
From: Greg Sherwood on 7 Jul 2009 02:49
On 07/07/2009, at 4:20 PM, Laurent Laville wrote:

> PEAR Announce a écrit :
>> The new PEAR package PHP_CodeSniffer-1.2.0RC3 (beta) has been
>> released at http://pear.php.net/.
>> Release notes
>> -------------
>> - You can now use @codingStandardsIgnoreStart and @...End comments
>> to suppress error messages (feature request #14002)
>> - A warning is now included for files without any code when
>> short_open_tag is set to Off (feature request #12952)
>> - You can now use relative paths to your custom standards with the
>> --standard cmd line arg (feature request #14967)
>> - You can now override magic methods and functions in PEAR
>> ValidFunctionNameSniff (feature request #15830)
>> - MySource IncludeSystemSniff now recognises widget action classes
>> - MySource IncludeSystemSniff now knows about unit test classes and
>> changes rules accordingly
>
>
> *What's wrong with PHPCS 1.2.0RC3 ?*
>
> I've just upgraded from 1.2.0RC2, and run it on many package and got
> tone of errors and warnings.

I don't get any errors on the CSS.php file, but I'm not testing on
Windows and don't have a Windows box handy to try it on.

I'll try it later.

In the meantime, can you email me the output from "phpcs -v HTML/
CSS.php" so I can see which standard it is using. Email me privately
so we don't pollute the list with all this output.

Greg
 | 
Pages: 1
Prev: This is a BUG
Next: HTML_QuickForms2