Re: [Coding Standards] Class-to-file convention

Paul M Jones wrote:

The section titled "Class to file convention" states:

Class-to-file convention All public classes must be in their own file with underscores replaced by directory separator, so that PEAR2_PackageName_Base class is always located in PEAR2/PackageName/Base.php (this is required to make autoload always work) Requirement Exceptions maybe made to this rule with approval from the PEAR Group

Allowing for personal exceptions to a fundamental rule like this seems out of place to me; appeals to the Group should be available for any/all the standards, or for none of them. I would say "no exceptions" to this rule.

On the other hand, dozens of files with dozens of smallish classes inside (see f.e. HTML_QuickForm2 in CVS) will negate all hypothetical performance benefits from require_once -> require transitions.