Re: merging Controversial changes back into PEAR2 Standards

> * 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 +1 Restricting it to PEAR2_Autoload only would be even better; are there cases where a 'custom solution' would be required? > * 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] 0 It's just a recommendation, so I'm Ok either way. > * use import statements at the top of the file to declare dependencies > explicitly -1 Why? I've probably missed something - are we allowing dependencies on certain namespaces of a package? If a package is installed, the entirety of it is there, so why would the current dependency system not work? Wow, that sums to 0. -- Anant