Extra characters in output of phpcs with WordPress standard

[KenCarlson]

I have downloaded and installed the latest version of phpcs and these WordPress standards. I am running this with Netbeans and XAMPP on a Windows 7 machine. In Netbeans, phpcs works fine with the PEAR standard, but with the WordPress standard it gives this error: [Fatal Error] :1:1: Content is not allowed in prolog.

I ran phpcs.bat from the Windows command line, and the WordPress standard works fine, except that I see 2-3 bytes of garbage characters at the very beginning of the report. Those bytes are not there with the PEAR standard. So I suspect that this is the problem. A few bytes of something are getting output before the XML

[mrchrisadams]

Hi Raptor2m!

Just a note, - this has been seen, I but I don't have a windows machine to look into this.

Is there a chance you could share a relevant screenshot or text output showing the problem?

[GaryJones]

Maybe a BOM added somewhere and being echoed out?

[Rarst]

Can reproduce:

Win7, confirm as specific to WP standard.

[Rarst]

I think the bad file is /Sniffs/WhiteSpace/OperatorSpacingSniff.php (I buffered includes and checked which file produces non-empty buffer) but I have no clue why or how it produces that output.

[westonruter]

💥

$ grep -rl $'\xEF\xBB\xBF' .
./Sniffs/WhiteSpace/OperatorSpacingSniff.php