Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25997
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 216.145.54.172 cause and error)
Message-ID: <45293676.1060902@php.net>
Date: Sun, 08 Oct 2006 10:33:42 -0700
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: Lukas Kahwe Smith <lsmith@php.net>
CC: Ralph Schindler <ralph@smashlabs.com>, internals <internals@lists.php.net>
References: <4526D167.1080309@smashlabs.com> <45274D24.7040206@php.net>
In-Reply-To: <45274D24.7040206@php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: is_readable and include path
From: pollita@php.net (Sara Golemon)

>> bool is_readable ( string filename [, bool use_include_path] )
> 
> we can always dream ..
> so far the answer has been that this parameter should never have been 
> added to fopen(), and that file_exists(), is_readable and friends should 
> never get this feature. IIRC the reason was that they should not be 
> reading the include path, however even proposing to be atleast able to 
> pass in an order list of search pathes has been shot down. nevermind the 
> common use case for such a feature.
> 
How about something which will save having to resolve that path twice?

$realpath = stream_resolve_include_path($relativepath);

if ($realpath && is_readable($realpath)) {
   $fp = fopen($realpath, 'rb', false);
} else {
   /* File isn't readable */
}

The code for doing this is all in there, it'd just need some quick 
exposing to userspace...

-Sara