Re: merging Controversial changes back into PEAR2 Standards

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

Basically, these three things would again become part of the PEAR2 coding standards and community standards proposal: * 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.

* 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]

+1, especially the part about it being a recommendation, not a requirement.

* use import statements at the top of the file to declare dependencies explicitly

-1. I don't think we should be defining rules on how to use namespaces/packages/whatever until they exist in a public release. At that point it will be very easy to see how they behave in actual use, and we can build rules around reality, not projections. -- Paul M. Jones <http://paul-m-jones.com> Solar: Simple Object Library and Application Repository for PHP5. <http://solarphp.com> Join the Solar community wiki! <http://solarphp.org> Savant: The simple, elegant, and powerful solution for templates in PHP. <http://phpsavant.com>