Description:
------------
The documentation about how relative includes work must be wrong. It states that the include path is not checked when any kind of path (relative or absolute) is given.

Note also the deficiency noted in bug #51569, also related to poor documentation of how the include path/include statement works.



Test script:
---------------
include('PHPUnit/Framework.php');


Expected result:
----------------
According to the documentation, I expect a warning about non-existent file PHPUnit/Framework.php, as this doesn't exist relative to the cwd or the directory of the script, but somewhere inside PEAR's repository (referenced in the include path).

Actual result:
--------------
The file is successfully found and included.