Re: Re: cvs: php4 /pear DB.php /pear/DBcommon.phperror.phpmysql.php result.php warning.php
| From: | Sterling Hughes | Date: | Mon, 04 Dec 2000 07:14:03 +0000 |
| Subject: | Re: Re: cvs: php4 /pear DB.php /pear/DBcommon.phperror.phpmysql.php result.php warning.php | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-506@lists.php.net to get a copy of this message | ||
> On Mon, 04 Dec 2000, Chuck Hagenbuch wrote:
> > I'm interested in other people's thoughts on this one - it certainly makes
> > sense to in general split classes out into new files. But some classes -
like
> > PEAR:: and PEAR_Error:: - are core functionality as well as being closely
> > related, so it makes sense to keep them in the same file.
> >
> > I don't really know what the performance factors are; I imagine that modern
> > OS's disk caching should take care of most of it, but not at least thinking
> > about it and trying to reduce disk hits seems irresponsible to me.
>
> I see no problems with having multiple classes in the same file as long
> as they are closely related.
>
I also agree. For example a class's error class (PEAR_Error related) should be
in the same file as the class itself.
-Sterling