Simon Mundy wrote:
Except that it is not for the framework to use -- it is for userland and separate specific classes would be better to use for that.

I disagree - Zend.php should be used as part of the coding standards for the sake of consistency and reusability.

A lot of the components use 'require_once' which would be better replaced with Zend::load(). Say - for example - in the distant future it was decided that the PEAR standard of underscores replacing directory separators was not such a good idea and a new scheme was chosen. We'd have to completely pull apart the framework to replace hardcoded require_once() calls with the new paths. But if we use Zend::load('Class') then there's only 1 place it needs updating. To my mind it follows the DRY principle very well and helps to create more readable, reliable code.
I agree with the premise, but I fail to see how Zend_Loader::load('Class') or Zend_Registry::getInstanceOf('Class', $args) would not do the same thing, but be a better separation of concerns.

Reply via email to