On 10/5/06, Richard Lynch <ceo@xxxxxxxxx> wrote:
include_path is a much more powerful and flexible construct which will save you an inordinate amount of trouble if you just figure out how it works and use it...
Point well taken Richard, thanks. I've always been curious, iIs there a point in which adding some number of paths to include_path causes a performance hit? If my application for example is spread out across 6 or 7 folders (controllers, models, library, plugins, scripts, etc etc), is it really better to shove all of those into include_path? Thanks, John W -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
