-- keith Pope <[email protected]> wrote (on Monday, 30 March 2009, 09:14 AM +0100): > Just writing a bit about Zend_Application and I noticed that there was > no easy way to change the suppressNotFoundWarnings in the autoloader. > It may be useful to have this as one of Zend_Applications options or > have a way of passing options to the autoloader via Zend_Application. > I know this can be done in a bootstrap resource but would be better if > you could pass suppressNotFoundWarnings during Zend_Application > instantiation.
Could you add an issue in the tracker asking for an autoloaderOptions key? I spaced this out entirely, but you're absolutely correct -- Zend_Application should take care of that. > Also when adding namespaces to the autoloader how are these used, say > I add MY_ and Zend_, this will load the SF_ and Zend_ namespaces using > the Zend Framework coding standard of _ = directory seperator? So, Zend_Loader_Autoloader was designed to allow specifying namespaced autoloaders. However, not all libraries use PEAR conventions -- symfony and eZcomponents come to mind here. In such cases, enforcing a _ separator between the vendor namespace and component/class name would be an artificial limitation. As such, you need to specify the full namespace for your component, including an underscore, to ensure that they are treated separately. (This is especially important in regards to differentiating ZendX and Zend -- the latter matches the former unless you use trailing underscores.) -- Matthew Weier O'Phinney Software Architect | [email protected] Zend Framework | http://framework.zend.com/
