Fix doc bug #52845 (Documentation wrong re includes with relative paths) by

adding clarifying text on what we actually mean by full and relative paths.


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@303377 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Adam Harvey 2010-09-15 03:55:24 +00:00
parent 7a69ac3da6
commit 910f0c46a5

View file

@ -20,10 +20,13 @@
<link linkend="errorfunc.constants.errorlevels.e-error">fatal error</link>.
</simpara>
<simpara>
If a path is defined (full or relative), the
<link linkend="ini.include-path">include_path</link> will be ignored altogether.
For example, if a filename begins with <literal>../</literal>, the parser will
look in the parent directory to find the requested file.
If a path is defined &mdash; whether absolute (starting with a drive letter
on Windows, or <literal>/</literal> on Unix/Linux systems) or relative to
the current directory (starting with <literal>.</literal> or
<literal>..</literal>) &mdash; the
<link linkend="ini.include-path">include_path</link> will be ignored
altogether. For example, if a filename begins with <literal>../</literal>,
the parser will look in the parent directory to find the requested file.
</simpara>
<simpara>
For more information on how PHP handles including files and the include path,