* doc/autoconf.texi (Limitations of Builtins) <case>: Mention

Tru64 ksh pattern matching bug.  Reported against Libtool by
Albert Chin <libtool@mlists.thewrittenword.com> and
Nicolas Joly <njoly@pasteur.fr>.

diff --git a/ChangeLog b/ChangeLog
index 97171af4e8ce7e95705fe0a86eb2e1e71fd88403..17c8f0cea0c2ad161fc193943066633966dbd3f4 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -24,6 +24,11 @@
        Reword to avoid some formatting glitches.
        * doc/installt.exi: Reword to avoid some formatting glitches.
 
+        * doc/autoconf.texi (Limitations of Builtins) <case>: Mention
+        Tru64 ksh pattern matching bug.  Reported against Libtool by
+        Albert Chin <libtool@mlists.thewrittenword.com> and
+        Nicolas Joly <njoly@pasteur.fr>.
+
 2005-06-06  Stepan Kasal  <kasal@ucw.cz>
 
        m4_cdr of one-member list was [[]] (one-member list containing an

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 67255fa524282417a0a455ec8851d70ab1ddbd1c..0c5ba7ca3c5618a4b3c77331a20dce9b1929061f 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -10899,6 +10899,16 @@ $
 Even with this, SunOS 5.7 ksh matches a backslash if the set contains any
 of the characters @samp{|}, @samp{&}, @samp{(}, or @samp{)}.
 
+Conversely, Tru64 @command{ksh} (circa 2003) erroneously always matches
+a closing parenthesis if not specified in a character class:
+
+@example
+$ @kbd{case foo in *\)*) echo fail ;; esac}
+fail
+$ @kbd{case foo in *')'*) echo fail ;; esac}
+fail
+@end example
+
 Some shells, such as Ash 0.3.8, are confused by an empty
 @code{case}/@code{esac}: