Re: What are the problems PEAR2 seeks to solve? [and a solution to the require_once debacle]

Hi, Gregory Beaver wrote:

It must be noted that the addition of namespaces changes a great deal. There is an uncommitted patch on php-internals adding autoload support to namespaces which will change things quite a bit. Because of that patch, using unqualified classnames no longer works with autoload if they share the same name as an internal class (like Exception), which will happen with this code: ... So perhaps by substituting the import statement for require_once, this will preserve the readability and maintainability?

I read the php-internals threads until my head started to hurt and I'd like to suggest once again that RFC in question should be split in parts, with those parts that people mostly agree upon being proposed soon and require_once-related stuff left until the proverbial dust settles on PHP namespace implementation. In any case, thank you Greg for this in-depth description, it was really helpful.