Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-11 Thread Andi Gutmans
At 03:19 AM 7/12/2001 +0200, Piotr Pawlow wrote: >"Brian Moon" <[EMAIL PROTECTED]> wrote: > > 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. > >What do you say about include loca

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-11 Thread Piotr Pawlow
"Brian Moon" <[EMAIL PROTECTED]> wrote: > 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. What do you say about include local($str), include_once local($str) ? Just one new function,

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-10 Thread Aral Balkan
>> If we choose to do it in Andi's way (no real drawbacks, considering it's downwards compatible for most practical purposes), we can do it within 4.0. This would be even better. To echo what Andrei said, "the sooner the better" :) I've personally been wishing for this for the longest time! Aral

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-10 Thread Zeev Suraski
If we choose to do it in Andi's way (no real drawbacks, considering it's downwards compatible for most practical purposes), we can do it within 4.0. At 16:15 10/7/2001, Andrei Zmievski wrote: >On Tue, 10 Jul 2001, Andi Gutmans wrote: > > Does others also think it should wait for 4.1 or later? If

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-10 Thread Andrei Zmievski
On Tue, 10 Jul 2001, Andi Gutmans wrote: > Does others also think it should wait for 4.1 or later? If so I'll leave it > for now (I'll have more free time :). It'd be really nice to have it as soon as possible. ;-) -Andrei * Change is the only constant. * -- PHP Development Mailing List

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Aral Balkan
>> Does others also think it should wait for 4.1 or later? I for one would love to see it in 4.1 -- IMVHO This would be a very important feature and a great improvement! Aral :) __ ([EMAIL PROTECTED]) New Media Producer, Kismia, Inc. ([EMAIL PROTECTED]) Adj. P

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
At 07:03 AM 7/10/2001 +0200, Jani Taskinen wrote: > >>I am still +1, but think it should be at least a 4.1 thing. > > > >Does others also think it should wait for 4.1 or later? If so I'll leave it > >I don't. But I consider this more as a bug than missing feature.. >So it should be fixed ASAP. :)

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Jani Taskinen
On Tue, 10 Jul 2001, Andi Gutmans wrote: >At 04:04 PM 7/9/2001 -0500, 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/ind

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
At 04:04 PM 7/9/2001 -0500, 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 in

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
- >>dealnews.com, Inc. >>Makers of dealnews & dealmac >>http://dealnews.com/ | http://dealmac.com/ >> >> >>- Original Message - >>From: "Andi Gutmans" <[EMAIL PROTECTED]> >>To: "Brian Moon" &

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Brian Moon
AIL 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 versio

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Vlad Krupin
"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: [PH

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread 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 cur

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
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

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Brian Moon
TECTED]>; <[EMAIL PROTECTED]> Sent: Monday, July 09, 2001 2:46 PM Subject: Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0. > At 12:03 PM 7/9/2001 -0700, Vlad Krupin wrote: > >Is it better to break things once or twice? Ok, not completely break, but >

RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Brian Tanner
ginal Message- From: Andi Gutmans [mailto:[EMAIL PROTECTED]] Sent: July 9, 2001 12:46 PM To: Vlad Krupin; Zeev Suraski Cc: Andrei Zmievski; [EMAIL PROTECTED] Subject: Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0. At 12:03 PM 7/9/2001 -0700, Vlad Krupin wrote: >Is i

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
At 12:03 PM 7/9/2001 -0700, Vlad Krupin wrote: >Is it better to break things once or twice? Ok, not completely break, but >now I have some code working with PHP4, later I will have some code that >will work with PHP4.1, and finally I will re-write it to work with the >latest-and-best PHP5. It i

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Vlad Krupin
Is it better to break things once or twice? Ok, not completely break, but now I have some code working with PHP4, later I will have some code that will work with PHP4.1, and finally I will re-write it to work with the latest-and-best PHP5. It is more like saying "Here is my script, you can run

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Vlad Krupin
I would *love* to see that! Vlad Andi Gutmans wrote: > Hey, > > I think one thing that bothers PHP developers is when they do: > include "../foo.inc"; > and in foo.inc they do: > include "bar.inc"; > > That bar.inc is not searched for in foo.inc's current directory > automatically. As we prett

RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Zeev Suraski
lled their file, and they might have to end up re-implementing >>existing workarounds anyway. Just a thought. >> >>-Brian Tanner >>-Original Message----- >>From: Zeev Suraski [mailto:[EMAIL PROTECTED]] >>Sent: July 9, 2001 5:48 AM >>To: Andi Gutmans >>C

RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
g workarounds anyway. Just a thought. > >-Brian Tanner >-Original Message- >From: Zeev Suraski [mailto:[EMAIL PROTECTED]] >Sent: July 9, 2001 5:48 AM >To: Andi Gutmans >Cc: [EMAIL PROTECTED] >Subject: Re: [PHP-DEV] Possible feature for current version of PHP or >P

RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Brian Tanner
] Possible feature for current version of PHP or PHP 4.1/5.0. 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

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
I actually had in mind something like option #4 but not exactly what Zeev wrote. I thought that what we could do is if cwd and include_path fail then try and open at the same directory level as the currently executing script. I think it can be done but haven't completely checked it from a techn

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Zeev Suraski
At 18:35 9/7/2001, Andrei Zmievski wrote: > > 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? Yep, that's what I meant. Zeev -- P

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Aral Balkan
> How about #3 for 4.1 and #2 for 5.0? This would be wonderful! Aral :) __ ([EMAIL PROTECTED]) New Media Producer, Kismia, Inc. ([EMAIL PROTECTED]) Adj. Prof., American University ¯¯ -- PHP Development Mailing List

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andi Gutmans
At 10:02 AM 7/9/2001 -0500, Andrei Zmievski wrote: >On Sun, 08 Jul 2001, Andi Gutmans wrote: > > Hey, > > > > I think one thing that bothers PHP developers is when they do: > > include "../foo.inc"; > > and in foo.inc they do: > > include "bar.inc"; > > > > That bar.inc is not searched for in foo.

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andrei Zmievski
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 >

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Zeev Suraski
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

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-09 Thread Andrei Zmievski
On Sun, 08 Jul 2001, Andi Gutmans wrote: > Hey, > > I think one thing that bothers PHP developers is when they do: > include "../foo.inc"; > and in foo.inc they do: > include "bar.inc"; > > That bar.inc is not searched for in foo.inc's current directory > automatically. As we pretty much always

RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-08 Thread Brian Tanner
uess as long as it doesn't add to ambiguity (would there be include_relative() or include($FilePath[,boolean relative])... could be useful. -Brian Tanner -Original Message- From: Andi Gutmans [mailto:[EMAIL PROTECTED]] Sent: July 8, 2001 9:15 AM To: [EMAIL PROTECTED] Subject: [PH

Re: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-08 Thread John Burroway
At 07:14 PM 7/8/01 +0300, Andi Gutmans wrote: >Hey, > >I think one thing that bothers PHP developers is when they do: >include "../foo.inc"; >and in foo.inc they do: >include "bar.inc"; > >That bar.inc is not searched for in foo.inc's current directory >automatically. As we pretty much always hav

[PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.

2001-07-08 Thread Andi Gutmans
Hey, I think one thing that bothers PHP developers is when they do: include "../foo.inc"; and in foo.inc they do: include "bar.inc"; That bar.inc is not searched for in foo.inc's current directory automatically. As we pretty much always have the expanded filename of the current executing scrip