I am -1 on yet another new function. Because, if you create a new
include_local or whatever, people are gonna want include_local_once and so
on and so forth.
I am alos -1 on making it an option. Do you know what a headache it is to
try and write and app like Phorum and mess with a million different server
setups.
Brian Moon
------------------------------------------
dealnews.com, Inc.
Makers of dealnews & dealmac
http://dealnews.com/ | http://dealmac.com/
----- Original Message -----
From: "Vlad Krupin" <[EMAIL PROTECTED]>
To: "Brian Moon" <[EMAIL PROTECTED]>
Cc: "Zeev Suraski" <[EMAIL PROTECTED]>; "Andi Gutmans" <[EMAIL PROTECTED]>; "Andrei
Zmievski" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 4:49 PM
Subject: Re: [PHP-DEV] Possible feature for current version of PHP or PHP
4.1/5.0.
> Andi, I definitely do like your approachl. I do not like that different
> versions of PHP will behave differently. That's what I was talking
> about. And it is a situation similar to what Brian described that
> prompted me to write to the list and see if we can come up with one
> solution which will stay, whether in version 4.1, or 5, or 5.5.
>
> I know that I have myriads of includes with a pretty extensive directory
> structure, and some scripts are having the same names. I have run into
> problems including the wrong file by mistake. I do not want to make that
> mistake easier to make. That's why I asked if it makes sense to leave
> include() as it is, and create another function/construct that will
> behave as described, and asked if that would be too much of a bloat. I
> can not judge that myself, for I do not know enough. If it is, discard
> that idea, but could we please implement something that will not change
> between verision 4.1 and 5 and hopefully later?
>
> Sorry, couldn't reply earlier - I was following up on the heated
> discussions here...
>
> Vlad
>
>
> Brian Moon wrote:
>
> >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]
>
>
>
--
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]
