Matthew Weier O'Phinney-3 wrote:
Now, as for the 'Zend_Application_Bootstrap_' prefix... This makes much
more sense when you consider it a namespace, as then each item under
that namespace has a discrete name:
namespace zend\application\bootstrap;
interface Bootstrapper {}
interface ResourceBootstrapper {}
abstract class BootstrapAbstract implements Bootstrapper, ResourceBootstrapper{}
class Bootstrap extends BootstrapAbstract {}
The point was to keep the various classes within the same component
namespace.
Thank you for explanation. The idea looks fine, but I think that it's better for developers to use the same convention in the framework. I mean using Zend_View, Zend_Application_Bootstrap and so on in version 1.8 and rename all classes to a new convention in the next one.
Matthew Weier O'Phinney-3 wrote:
> 2. Why in config file you are using PATH_SEPARATOR for includePaths? This
> can be a problem if the application has to be installed on 2 different
> systems which uses different PATH_SEPARATOR - in such case you should use
> different config files for these systems, and of course it's better to have
> one. IMHO in Zend_Application::setIncludePaths you should use for example
> ";" for implode and then PATH_SEPARATOR for set_include_path as it is now
Can you point out where we are doing that?
Oops, my mistake, it was just a quick look and now I see that this is ok, so forget the question
regards,
jk
