Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> * doc/autoconf.texi (Limitations of Builtins) <case>: Mention
> Tru64 ksh pattern matching bug.
Thanks. I installed the following slightly-different patch into
autoconf.
--- autoconf.texi 8 Jun 2005 07:13:50 -0000 1.907
+++ autoconf.texi 8 Jun 2005 07:55:29 -0000 1.908
@@ -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:
+
[EMAIL PROTECTED]
+$ @kbd{case foo in *\)*) echo fail ;; esac}
+fail
+$ @kbd{case foo in *')'*) echo fail ;; esac}
+fail
[EMAIL PROTECTED] example
+
Some shells, such as Ash 0.3.8, are confused by an empty
@code{case}/@code{esac}:
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
