Re: Re: 1 class = 1 file?
| From: | till | Date: | Sat, 12 May 2007 16:54:55 +0000 |
| Subject: | Re: Re: 1 class = 1 file? | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-46748@lists.php.net to get a copy of this message | ||
On 5/12/07, Mark Wiesemann <wiesemann@php.net> wrote:
Hi, Lukas Kahwe Smith wrote: David Soria Parra wrote:I thought I read this somewhere in the CS when I started working on my package. I also remember someone reminded me to put my Exception into a seperate file. Maybe that was even you, Mark? ;-) IMO and for clarity, it's one class per file. Having too many exceptions to the rule just weakens the "standard". And maybe - if it's not hidden somewhere already - this should be added to the docs. Cheers, TillThere is no rule that mandates one class per file really. Personally I have always gone by the rule 1 file file per public class. Yes, this makes sense, and this was also what we were thinking about. Thanks for the quick replies.If it is just for internal purpose it should be okay to include into one file.