From: Akim Demaille <akim@epita.fr>
Date: Tue, 14 Nov 2000 14:22:13 +0000 (+0000)
Subject: * doc/autoconf.texi (Limitations of Builtins): Comment `true'.
X-Git-Tag: autoconf-2.50~421
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2014a4b07eb84e51cdc9aba18ba7c6af0b394885;p=thirdparty%2Fautoconf.git

* doc/autoconf.texi (Limitations of Builtins): Comment `true'.
---

diff --git a/ChangeLog b/ChangeLog
index bb53cf420..8536b9f90 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2000-11-14  Akim Demaille  <akim@epita.fr>
+
+	* doc/autoconf.texi (Limitations of Builtins): Comment `true'.
+
 2000-11-14  Akim Demaille  <akim@epita.fr>
 
 	* BUGS: New file.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 55145be48..2f5f1fce4 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -5701,6 +5701,22 @@ $ exit
 @noindent
 Fortunately this bug affects only trap.
 
+@item @command{true}
+@cindex @command{true}
+@cindex @command{:}
+Don't worry: as far as we know @command{true} is portable.
+Nevertheless, it's not always a builtin (e.g., Bash 1.x), and the
+portable shell community tends to prefer using @command{:}.  This has an
+funny side effect: when asked whether @command{false} is more portable
+than @command{true} Alexandre Oliva answered
+
+@quotation
+In a sense, yes, because if it doesn't exist, the shell will produce an
+exit status of failure, which is correct for @command{false}, but not
+for @command{true}.
+@end quotation
+
+
 @item @command{unset}
 @cindex @command{unset}
 You cannot assume the support of @command{unset}, nevertheless, because