From a89e34ea3ddb48ee7f84b5383ddde1567c33449c Mon Sep 17 00:00:00 2001
From: Akim Demaille <akim@epita.fr>
Date: Tue, 2 Oct 2001 14:37:07 +0000
Subject: * lib/m4sugar/m4sh.m4 (AS_SHELL_SANITIZE): Just source 40.lineno
 instead of exec'ing to preserve $0 and $@.

---
 doc/autoconf.texi | 9 +++++++++
 1 file changed, 9 insertions(+)

(limited to 'doc')

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 354f8dc4..0d49600c 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -8298,6 +8298,7 @@ the @samp{x} into account later in the pipe.
 @table @asis
 @item @command{.}
 @prindex @command{.}
+@prindex @command{source}
 Use @command{.} only with regular files (use @samp{test -f}).  Bash
 2.03, for instance, chokes on @samp{. /dev/null}.  Also, remember that
 @command{.} is not expected to look in the current directory, hence you
@@ -8549,6 +8550,7 @@ processing as soon as a non-option argument is found.  Therefore, use
 set x $my_list; shift
 @end example
 
+
 @item @command{shift}
 @c ------------------
 @prindex @command{shift}
@@ -8556,6 +8558,12 @@ Not only is @command{shift}ing a bad idea when there is nothing left to
 shift, but in addition it is not portable: the shell of @sc{mips
 risc/os} 4.52 refuses to do it.
 
+
+@item @command{source}
+@c -------------------
+See the item @command{.} above.
+
+
 @item @command{test}
 @c -----------------
 @prindex @command{test}
@@ -8575,6 +8583,7 @@ statement, keep in mind that they have equal precedence.
 You may use @samp{!} with @command{test}, but not with @command{if}:
 @samp{test ! -r foo || exit 1}.
 
+
 @item @command{test} (files)
 @c -------------------------
 To enable @code{configure} scripts to support cross-compilation, they
-- 
cgit v1.2.1