Re: [Coding Standards] Loading all files at once

On 7/9/07, Arnaud Limbourg <arnaud@limbourg.com> wrote:

Matthew Weier O'Phinney wrote: I'm clueless as to what you're referring to here. I use PEAR, Solar, and Zend Framework regularly, and typically have them installed to a common directory, leaving me with a simple include_path of: .:/path/to/pear and never have a problem, even when using __autoload() (check out Zend_Loader::registerAutoload() for a PEAR-friendly spl_autoload implementation, btw). Could you please elaborate on the "include_path mess" that you're trying to solve with this? It is usually a problem with shared hosts eve though set_include_path() exists a lot of people don't seem to know about it/don't use it/cannot use it.

I see how easy coding and adoption rates seem to come into account here. Then again, as you stated: the means are already available and I don't honestly see the argument where you make it easier for people who don't want to read docs at all. Even the setup on a shared host (set_include_path) or .htaccess style manipulation of the php.ini setting is a no-brainer rather. Of course you have to know what you are doing, but why is that an issue here? I really fail to understand why it has to be -so- easy for people to use PEAR when (in real-life) you'd never want them to write any PHP for you anyway. 2 European cents from my end. Till