Re: [Coding Standards] Loading all files at once

Paul M Jones wrote:

Try making "what" work without include_path? Maybe I've been missing your point all along. Are you saying that you want PEAR2 packages always to be completely independent of include_path? If so, I don't see how setting an include_path is a problem for anyone other than neophyte PHP developers. Personally, I expect good libraries to follow the PEAR standards, which means name-spacing, and living in the PEAR directory -- which means setting that one include-path value.

This sentence from the Introduction of the document is a big reason behind the change: The new PEAR2 repository of code is designed for both installation by the Pyrus installer and unzip-and-go. There are existing rules in the PEAR repository which need to be revised. This document itemizes all the changes. The important word is "unzip-and-go". unzip-and-go requires that PEAR2 to be at least optionally include_path independent. If there is a better solution then allfiles.php to make that work i'm all for it. I'm even testing various options and benchmarking them. But the current system has problems, I'm not suggesting we change it because it sounds like a fun thing to do. I'm hoping to get some benefits here. Allow PEAR2 to work without setting the include_path (this allows unzip-and-go, easy packaging of pear inside your own apps, easy use of pear inside of plugins for other projects) Make sure PEAR2 is fast in opcache environments (this being the people who care most about performance) Make sure PEAR2 truly works with __autoload (some people like autoload) Make it very easy to start using a PEAR package Make it possible to do super custom stuff like using PEAR in a phar You may disagree that these points are important, but I do hope you understand that there is some a reason for me wanting some change here. -josh