summaryrefslogtreecommitdiff
path: root/doc/ref/api-evaluation.texi
diff options
context:
space:
mode:
authorAndy Wingo <wingo@pobox.com>2013-01-20 20:26:59 +0100
committerAndy Wingo <wingo@pobox.com>2013-01-22 12:06:59 +0100
commit84f5a8251710c7d2a01590aa083d9dd409a56279 (patch)
tree7465279f6c143a4635c50408fc67783b3e3b1a83 /doc/ref/api-evaluation.texi
parentf0b6d8c71d2be9d93b48a921a6388fa5acdbd94b (diff)
downloadguile-84f5a8251710c7d2a01590aa083d9dd409a56279.tar.gz
`include' relative paths relative to including file
* module/ice-9/psyntax.scm (include): Like `load', interpret relative paths as being relative to the file that does the `include'. * doc/ref/api-evaluation.texi: Update docs.
Diffstat (limited to 'doc/ref/api-evaluation.texi')
-rw-r--r--doc/ref/api-evaluation.texi3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/ref/api-evaluation.texi b/doc/ref/api-evaluation.texi
index f80d7ad7f..0ffb5014e 100644
--- a/doc/ref/api-evaluation.texi
+++ b/doc/ref/api-evaluation.texi
@@ -1161,6 +1161,9 @@ parts of programs together at expansion-time instead of at run-time.
Open @var{file-name}, at expansion-time, and read the Scheme forms that
it contains, splicing them into the location of the @code{include},
within a @code{begin}.
+
+If @var{file-name} is a relative path, it is searched for relative to
+the path that contains the file that the @code{include} for appears in.
@end deffn
If you are a C programmer, if @code{load} in Scheme is like