Issue Type: Improvement Created: 2009-07-25T22:47:17.000+0000 Last Updated: 2009-07-26T05:26:44.000+0000 Status: Resolved Fix version(s): - 1.6.0 (02/Sep/08)
Reporter: Ramon Henrique Ornelas (ramon) Assignee: Matthew Weier O'Phinney (matthew) Tags: - Zend_Cache
Related issues: - ZF-3875
All ZF components should be loosly coupled and be able to be used alone without other components if possible.
Zend_Cache_Backend for example:
<pre class="highlight"> // Create a default logger to the standard output stream Zend_Loader::loadClass('Zend_Log_Writer_Stream');
A simple require_once would be faster and would decouple it from Zend_Loader, which makes it possible to use Zend_Cache without Zend_Loader. There are a few other places in Zend_Cache where this should also be decoupled.
Posted by Ramon Henrique Ornelas (ramon) on 2009-07-25T23:01:51.000+0000
Method _isReadable in class Zend_Cache, reported in the issue ZF-2891
change to method Zend_Loader::isReadable
Posted by Matthew Weier O'Phinney (matthew) on 2009-07-26T05:26:23.000+0000
This issue was basically eliminated with 1.8.1. For that version, I scrubbed all classes that used Zend_Loader to have a check for "class_exists()" prior to falling back on Zend_Loader. This allows user-defined autoloading to be used, and only uses Zend_Loader in situations where nothing was defined during autoloading.
We will not use require_once instead, as this would lead to code duplication of the class => file resolution logic (a point that's particularly important as we start looking towards 2.0 and adopting the use of namespaces).
Have you found an issue?
See the Overview section for more details.