ZF-4139: Zend_Loader::autoload() generates warnings instead of returning false without any output.


The following code

require_once 'Zend/Loader.php';


Produces output:

{panel} Warning: Zend_Loader::include_once(Zend/FooBar/Magic/Abstract.php): failed to open stream: No such file or directory in /home/cawa/ZendFramework/svn/framework/branches/release-1.6/library/Zend/Loader.php on line 83

Warning: Zend_Loader::include_once(): Failed opening 'Zend/FooBar/Magic/Abstract.php' for inclusion (include_path='.:/home/cawa/ZendFramework/svn/framework/branches/release-1.6/library/:/home/cawa/ZendFramework/svn/framework/branches/release-1.6/incubator/library/:/home/cawa/ZendFramework/svn/framework/branches/release-1.6/tests/:/home/cawa/ZendFramework/svn/framework/branches/release-1.6/incubator/tests/:/usr/share/pear:/usr/share/php') in /home/cawa/ZendFramework/svn/framework/branches/release-1.6/library/Zend/Loader.php on line 83 {panel}


It's not actualy Zend_Loader problem, but some another which was masked by [ZF-4002].

Once [ZF-4002] was resolved it problem appears.

It also produces the following output: {panel} Catchable fatal error: Argument 1 passed to Zend_Service_Technorati_Author::__construct() must be an instance of DOMElement, string given in /home/cawa/ZendFramework/svn/framewo rk/branches/release-1.6/library/Zend/Service/Technorati/Author.php on line 95 {panel}

And breaks Unit tests execution

The problem is actualy caused by PHPUnit patch applied earlie.

Patch affected set_error_handler() behavior for PHPUnit system. Sebastian Bergmann had a comment, that PHPUnit code was actually correct, but PHP had a documentation bug in a set_error_handler() description.

That's really so. The problem we had at that time was actually caused by [ZF-4002] issue. Patched PHPUnit produced output and behaviour mentionet above when [ZF-4002] was fixed.

Unit tests had passed correctly just after PHPUnit environment fix.

Nevertheless, several places, which need set_error_handler() processing improvement, were found while researching this issue. So it's still opened.


Updating for the 1.6.0 release.