Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4611
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <021801c38741$b34407f0$0702a8c0@titan>
To: "Lukas Smith" <smith@backendmedia.com>, <internals@lists.php.net>
References: <005801c3873e$38c71880$4d00a8c0@vandal>
Date: Tue, 30 Sep 2003 11:57:54 +0100
Organization: The Brain Room Ltd.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] file_exists and array_merge_clobber
From: wez@thebrainroom.com ("Wez Furlong")

Using the include path for file_exists doesn't sound useful to me, for
similar reasons as those for not allowing to write a file in the include
path - which file are you actually writing to?  What if someone puts a file
with the same name earlier in the include path and so on.

What is probably better is some kind of generic path-searching function that
returns the full path to the first file in the include_path (or some other
path).

--Wez.

----- Original Message ----- 
From: "Lukas Smith" <smith@backendmedia.com>
To: <internals@lists.php.net>
Sent: Tuesday, September 30, 2003 11:32 AM
Subject: [PHP-DEV] file_exists and array_merge_clobber


> Hi,
>
> We have a new intern who got right to work to improve file_exists() to
> also be able to check the include_path similar to how fopen() can.