On Mon, 09 Jul 2001, Zeev Suraski wrote:
> Yeah, this has been requested several times.
> I think that changing the cwd to the directory of an included file makes 
> good sense.  It is, indeed, downwards incompatible and may break existing 
> applications.  We have 4 options:
> 1.  Do nothing
> 2.  Make include() and friends change directory to the directory of the 
> file they include.  This makes the most sense, but may break existing apps.
> 3.  #2, only make it optional
> 4.  Add the directory of the included file to the include_path when the 
> included file is being executed.  It can get a bit nasty with nested 
> includes, even though I think it should work.  It's also a bit tricky to 
> implement, as the engine doesn't know about include_path (at least right now).
> I'm leaning towards #3, even though I don't like the 
> yet-another-runtime-option.  It may be justified if we say we're phasing 
> out the old functionality in PHP 5.0.

How about #3 for 4.1 and #2 for 5.0?

* If it's never finished, you can't prove it doesn't work. *

PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to