Re: merging Controversial changes back into PEAR2 Standards

On Sep 22, 2007, at 5:48 PM, Gregory Beaver wrote:

* eliminate require_once/include_once/require/include from PEAR packages as a means of loading classes, and instead rely upon users to either use PEAR2_Autoload or a customized loading solution of their own creation * recommend using class_exists() to throw an exception with helpful error message when loading drivers [this is optional, and would be a recommendation, not a requirement] * use import statements at the top of the file to declare dependencies explicitly

1. +1 2. +1 (only if it stays optional) 3. 0/leaning toward -1 Why would want to import dependencies? Wouldn't it be better to promote using the entire namespaced code within the library? -T