Performance Consideration of 1 class per file

PEAR is considering stipulating 1 class per file, for the packages. - one of the concerns raised is performance. While this is true for a non-cache compiled situation (where performance is less of an issue) - would anyone care to comment on the implications when using the Zend Optimizer or APC, on how significant the impact of this would be. - looking at typical application where the number of files included in the code with may jump from 20->30 included files.. From my understanding, if you where looking for performance, you would probably have a cache expiry which would mean very few stat (if any) calls based on these addition includes.. - hence negating the issue.. Thanks Alan -- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com