Re: Re: Performance Consideration of 1 class

From:	Lukas Smith	Date:	Mon, 26 Apr 2004 13:41:58 +0000
Subject:	Re: Re: Performance Consideration of 1 class
References:	1 2 3 4 5 6 7 8	Groups:	php.pear.dev
Request:	Send a blank email to pear-dev+get-28367@lists.php.net to get a copy of this message

Chuck Hagenbuch wrote:

Quoting Sérgio Carvalho <sergio.carvalho@portugalmail.com>:
Based on this, I'd wager that using one class per file is better, even performance-wise. The brunt of the work is in the processing of the code (allocate/parse/compile), so any chance of not including code means time savings. Developers can only choose not to include a class if it is in a separate file.
... but if a pair of classes is *always* needed together, especially a set of small utility classes, then *requiring* them to live in seperate files is just plain silly. Why do you want to mandate this?

to me its helps in finding relevant code quicker. This both from the users and from the computers POV (enabling stuff like autoload to work cleanly with minimal guess work). regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07