Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

This is expected, and we can not change this as it will break a lot of scripts.

I'm asking for an addition, not a modification.

What kind of scripts would be broken if you search additional paths (after searching in the old way)?

And doesn't the documentation claim to already search relative to the script dir?

> and then in include_path relative to the directory of current script.

Oops, forgot to reopen.

PHP CLI "does not change the working directory to that of the script" (c) http://www.php.net/manual/en/features.commandline.php
In your case documentation says about other SAPIs.

I'm not asking for PHP (CLI) to change the cwd to that of the script.
I'm only asking for PHP to look for files *relative to the directory of the current script*, as the documentation claims it does.
Note that the directory of the current script is *not* equivalent to the cwd (current working directory).

> Files for including are first looked in include_path relative to the current working directory and then in include_path relative to the directory of current script.

All other SAPIs will chdir to the scripts directory. CLI will not. This is not a bug, so please don't reopen this report. 

You can always use:

include dirname(__FILE__).'/../1.php';

to solve your problem with relative paths in includes.

> All other SAPIs will chdir to the scripts directory. CLI will not.

Isn't that what Tony said too?

That doesn't matter. It will NOT change and NOT added. Please stop reopening this bug.

In that case, please update your documentation so it doesn't say it'll search relative to the directory of current script.

>In that case, please update your documentation so it 
>doesn't say it'll search relative to the directory of 
>current script.
All SAPIs except CLI DO search relative to the directory of current running script.
But you're using CLI and this feature is documented too.

So exactly where is that documented?
At http://php.net/include/ I see no exceptions for CLI and at http://php.net/manual/en/features.commandline.php I see no exceptions for include.

It does say "It does not change the working directory to that of the script. (-C and --no-chdir switches kept for compatibility)", but that's not relevant, as the include docs say it searches the directory of the current script, not the current working directory.
If your implementation relies on the current working directory being the directory of the current script, then your implementation (of this docs/specs) is wrong.

"Files for including are first looked in include_path relative to the current working directory and then in include_path relative to the directory of current script." in include() page. Current working directory can be something different than directory of a script.

> Current working
directory can be something different than directory of a script.

I understand, but apparently your implementation doesn't.
Why else would "include('../1.php');" fail?

You are right, documentation is not absolutely clear. Documented behavior is valid only if you don't go to upper directory in include.

b/2.php: <?php include "c/3.php"; ?>
b/c/3.php: b/c/3
`php b/2.php` works as documented - prints b/c/3 (if c/3.php doesn't exist).

I will update the docs.

"If filename begins with <literal>../</literal>, it is looked only in include_path relative to the current working directory."

This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation better.