From 910f0c46a54bd8773d31738edf9397e712e3196a Mon Sep 17 00:00:00 2001
From: Adam Harvey <aharvey@php.net>
Date: Wed, 15 Sep 2010 03:55:24 +0000
Subject: [PATCH] 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
---
 language/control-structures/include.xml | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/language/control-structures/include.xml b/language/control-structures/include.xml
index e5a8c3cc7c..9a96bb53be 100644
--- a/language/control-structures/include.xml
+++ b/language/control-structures/include.xml
@@ -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,