Re: Re: Performance Consideration of 1 class

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? -chuck -- "Regard my poor demoralized mule!" - Juan Valdez