> Zend_Acl ==> Zend_Acl_Resource_Interface, Zend_Acl_Role_Interface,
> Zend_Acl_Role_Registry, Zend_Acl_Assert_Registry...
>
> Regard, Stan Vassilev
Stan, ZF doesn't use namespaces yet. This is not namespaced code.
Namespaced code requires different convention
(http://framework.zend.com/wiki/display/ZFPROP/Naming+conventions+for+2.0+-+Matthew+Ratzloff).
In namespaced code there cannot be class Interface in namespace
Zend\Acl\Role. There must be class RoleInterface in Zend\Acl namespace.
Similary class Zend_Acl become Acl in Zend\Acl namespace. So look at the
code with namespace-eyes. Classes Zend_Acl, Zend_Acl_Resource_Interface,
Zend_Acl_Role_Interface... will exist in one namespace.
I've checked that wiki page before, and I'm following with interest how they
end up naming those, but that changes nothing.
Today, Zend_Acl uses Zend_Acl_Resource_Interface.
Tommorow, Zend\Acl uses Zend\Acl\ResourceInterface (or similar).
The fact is, PHP frameworks and especially Zend use plenty of factories and
facade classes, which by definition reach into inner-more classes and
provide simplified paradigm to the "outside world".
The Interface and Exception classes won't stay like this, but they'll still
be inside a subnamespace.
Regards, Stan Vassilev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
