Description: ------------ The bug has been previously reported (#17652) but was marked as bogus. I added a comment and a patch to that bug report, but will add them again here. Test script: --------------- class Autoload { static public $classes = array( // ... ); static public function load($class) { $className = strtolower($class); if (isset(static::$classes[$className])) { require dirname(__DIR__) . static::$classes[$className]; } } } Expected result: ---------------- No errors Actual result: -------------- If something like the above code is in a PHP script when trying to build a package pear will inform you that the file has invalid php code. The reason is that the Validator.php class only allows T_WHITESPACE and T_STRING in front of the T_DOUBLE_COLON. If you change the source to "self::$classes" instead of "static::$classes" pear does not complain.

Added patch support_late_static_binding.

I don't maintain PEAR

Can you provide me with exactly the code (a stripped down version is fine). I can run the code below through the source analyzes function just fine without any errors being raised.

You can clone a repos of mine from github and run pear package in that dir to get the error: christer@aurora:~$ git clone git://github.com/christeredvartsen/sqldiff.git ... christer@aurora:~$ cd sqldiff/ christer@aurora:~/sqldiff$ pear package Analyzing SqlDiff/Database/Table/Column/Abstract.php ... Warning: Parser error: invalid PHP found in file "./SqlDiff/Version.php" Warning: Parser error: invalid PHP found in file "./SqlDiff/Autoload.php" I'm getting the Parser error above with PEAR-1.9.1. After applying my patch I'm not getting any warnings.

The files that generated parse errors are: https://github.com/christeredvartsen/sqldiff/blob/0.0.3/SqlDiff/Autoload.php https://github.com/christeredvartsen/sqldiff/blob/0.0.3/SqlDiff/Version.php

Interesting, can not get the check function to fail on that code; Will have to test it via packaging up the code.

This bug has been fixed in SVN. 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. Found the issue, test framework was acting up