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

From: Date: Mon, 09 Jul 2007 23:44:57 +0000
Subject: Re: [Coding Standards] Class-to-file convention
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-47344@lists.php.net to get a copy of this message
On 7/9/07, Paul M Jones <pmjones@ciaweb.net> 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.
I agree that as the group, we should not be making exceptions. We are not imperialistic :P No execption to this rule is also my opinion.
-- 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> -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
-- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18

« previous php.pear.dev (#47344) next »