-1 for the idea. I think using include_path for realpath() goes
against the code logic that should be applied by realpath.
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Is it worth even attempting to create a patch and submitting it to do
the following:
string realpath ( string path [, bool use_include_path])
or will it be shot down?
There must be a way to find the full path to a file that resides in one
of the include paths no? I can understand not wanti
Sara Golemon wrote:
bool is_readable ( string filename [, bool use_include_path] )
we can always dream ..
I prefer the word "mature" instead of dream ;)
How about something which will save having to resolve that path twice?
$realpath = stream_resolve_include_path($relativepath);
if ($re
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
Ralph Schindler wrote:
In the spirit of fopen's optional [, bool use_include_path].. is this
something that can be added to is_readable?
ie:
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
