It is not so much BC. It is more like unexpected new behavior.
As of now, a bad programmer might have this:
/www/site.com/include/file.php
/www/site.com/include/config.php
/www/site.com/index.php
/www/site.com/config.php
if index.php includes include/file.php which includes "config.php", the
config in the main dir gets included.
Now, in the future, if the main config.php is not there, the one in the
include file gets included. Now, granted, this may not be the best case,
but it would cause some confusion if someone was not well aware of this
change.
I am still +1, but think it should be at least a 4.1 thing.
Brian Moon
------------------------------------------
dealnews.com, Inc.
Makers of dealnews & dealmac
http://dealnews.com/ | http://dealmac.com/
----- Original Message -----
From: "Andi Gutmans" <[EMAIL PROTECTED]>
To: "Brian Moon" <[EMAIL PROTECTED]>; "Vlad Krupin" <[EMAIL PROTECTED]>; "Zeev
Suraski" <[EMAIL PROTECTED]>
Cc: "Andrei Zmievski" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 3:44 PM
Subject: Re: [PHP-DEV] Possible feature for current version of PHP or PHP
4.1/5.0.
> At 03:43 PM 7/9/2001 -0500, Brian Moon wrote:
> >That is not completely true. If there is a file in the included scripts
dir
> >that has the same name as one in the including scripts dir, that would
cause
> >some unexpected problems.
>
> Well as I would only resort to looking according to the current file if
all
> other things fail (cwd and include_path) I can't see how it would break
BC.
>
>
> >I still like the idea.
>
> Thanks :)
>
> Andi
>
>
>
--
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]
