Description: ------------ It would be nice if PHP_CodeSniffer would generate output in an XML format so that the report can be utilized a little easier. Ideally, PHP_CodeSniffer could utilize some sort of logging capability so that various output formats could be used. Until that time I've created a simple patch which allows the report to be output in an XML format.

Great idea. There are functions that output the two different report formats at the moment (full and simple). I've been wanting to pull these out into classes so that more can be added easily. I might do that instead of adding this patch, and then create a new report format based on your XML output.

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. I didn't bother creating any additional report classes because I don't think there are going to be an huge number of report formats. Instead, I applied your patch but broke the different reports into methods. You can print the new XML report using the "--report=xml" command line arg. Thanks for the patch!