Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4630
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 1 Oct 2003 04:06:51 -0400
To: internals@lists.php.net
Message-ID: <20031001080650.GA16469@csh.rit.edu>
Mail-Followup-To: internals@lists.php.net
References: <005801c3873e$38c71880$4d00a8c0@vandal> <021801c38741$b34407f0$0702a8c0@titan> <20030930181433.30748.qmail@pb1.pair.com> <3F7A8997.5010703@php.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F7A8997.5010703@php.net>
Subject: Re: [PHP-DEV] file_exists and array_merge_clobber
From: jon@php.net (Jon Parise)

On Wed, Oct 01, 2003 at 10:00:23AM +0200, Hartmut Holzgraefe wrote:

> the whole point about this additional feature is that you can use it to 
> check
> for include file existance before the actual include:
> 
> if (file_exists("somefile.php", true)) {
>   include "somefile.php";
> }
> 
> IMHO this case is common enough so that it deserves a native C 
> implementation
> either as an option to file_exists() or as a seperate function like
> file_exists_in_path()
 
If we're really going to go down this road, why not implement it in a
more generic, reusable way:

    file_exists("somefile.php", ini_get('include_path'))

That would give us some additional mileage out of the change.

For the record, I'm -0 on this.  I'd be -1 if it wasn't so obviously
optional.

-- 
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)