Re: include_path question

> Any idea why it was decided "a zillion years ago" that if you define an > include_path scripts from the current directory won't be opened unless the > include_path includes .? > For example if you have a script: > /path/to/script.php > which is your main script, i.e. PATH_TRANSLATED > then include"foo.php" from within script.php won't open /path/to/foo.php > unless include_path has "." or include_path is not defined at all. > > Is this how ppl remember it? Why is it like this? I suppose the logic was to make it consistent with the notion of a search path. If you provide a search path you expect PHP to honour this path and not open files from anywhere outside of the given search path. We could make an exception for "." but are you actually seeing people getting confused over this? It has bee this way for a long time. -Rasmus