Edit report at http://bugs.php.net/bug.php?id=52847&edit=1
ID: 52847
Updated by: ahar...@php.net
Reported by: mail_ben_schmidt at yahoo dot com dot au
Summary: Files to include are always searched for in current
directory
-Status: Open
+Status: Duplicate
Type: Bug
Package: Scripting Engine problem
Operating System: Mac OS X 10.6.2
PHP Version: 5.3.2
Block user comment: N
New Comment:
This is intended behaviour: php_resolve_path() includes a fallback case
at the end to search the directory the currently executing file lives in
if all else fails.
I'll update the documentation. Duping to doc bug #51569.
Previous Comments:
------------------------------------------------------------------------
[2010-09-15 03:32:15] mail_ben_schmidt at yahoo dot com dot au
Actually, this may be a behaviour problem, not a documentation problem.
------------------------------------------------------------------------
[2010-09-15 03:26:04] mail_ben_schmidt at yahoo dot com dot au
Description:
------------
The documentation at include and include_path suggests that the current
directory will not be searched if a '.' is not in include path. Even
though I can see no reason (e.g. in the source code referred to by bug
#51569) that the current directory should be searched, it can be
demonstrated that it is.
See also bug #51569 and bug #52845 for further include_path
documentation deficiencies.
Test script:
---------------
1. Place in a file 'test/test.php':
set_include_path('/bin'); // won't find any php files here!
include('another.php');
2. touch another.php
3. php test/test.php
Expected result:
----------------
Warning that another.php cannot be found.
Actual result:
--------------
No warning.
N.B. In line with the undocumented feature mentioned in bug #51569, if
another.php is moved to test/another.php, it is still found also,
because it is in the directory of the running script.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=52847&edit=1
