Description: ------------ Anonymous functions in PHP 5.3 now emit E_NOTICE in Generic_Sniffs_Formatting_DisallowMultipleStatementsSniff on lines 66 a 67. Also, they raise many false positives in following sniffs: * Squiz_Sniffs_PHP_InnerFunctionsSniff * Squiz_Sniffs_Scope_MethodScopeSniff * Generic_Sniffs_Functions_OpeningFunctionBraceBsdAllmanSniff (I believe anonymous functions should have bracket on the same line as function keyword) * Squiz_Sniffs_PHP_NonExecutableCodeSniff and possibly others. Test script: --------------- <?php class User_Data_Memcache implements User_Data_Source { public function getData(User_Interface $user) { $fallback = $this->fallback; return $this->find(self::CACHE_KEY_EXTENDED . $user->username(), function() use ($fallback, $user) { return $fallback->getData($user); }); } }

PHP_CodeSniffer core has support for closures, but each sniff needs to check for them using the core functions. I've been fixing sniffs as I find them, so this task is ongoing.

Considering this is an ongoing feature request, I'm going to close it and just deal with any issues as bug reports.

Would it be possible to link to such bug reports from this feature request or other easily-findable place? I'm currently working on a couple of projects that have been using the PEAR sniffs with the attitude "we shouldn't have to write our own code standards..."