* doc/autoconf.texi (Limitations of Builtins): More about

case/esac.

diff --git a/ChangeLog b/ChangeLog
index 95042805da979c8050b27c6f7b59e8510060db01..550e628155fb468f496c058f308152c9c0718555 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2002-02-07  Akim Demaille  <akim@epita.fr>
+
+       * doc/autoconf.texi (Limitations of Builtins): More about
+       case/esac.
+
 2002-02-06  Akim Demaille  <akim@epita.fr>
 
        * lib/autoconf/status.m4 (_AC_OUTPUT_COMMANDS): Don't output empty

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 5f3078f1ae7578370163947fea33c80c7a5ce6d2..8c354da85b01c158c5b3abe8d00336555a6a7b31 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -8456,6 +8456,23 @@ bash-2.02$ @kbd{case /tmp in [\\/]*) echo OK;; esac}
 OK
 @end example
 
+Some shells, such as Ash 0.3.8, are confused by empty
+@code{case}/@code{esac}:
+
+@example
+ash-0.3.8 $ @kbd{case foo in esac;}
+@error{}Syntax error: ";" unexpected (expecting ")")
+@end example
+
+Many shells still do not support parenthesized cases, which is a pity
+for those of us using tools that rely on balanced parentheses.  For
+instance, Solaris 2.8's Bourne shell:
+
+@example
+$ @kbd{case foo in (foo) echo foo;; esac}
+@error{}syntax error: `(' unexpected
+@end example
+
 
 @item @command{echo}
 @c -----------------