Re: AC_CONFIG_COMMANDS does not handle an empty second argument.

[Akim Demaille]

| > I'd like to know what shell you used to document this.  None of the
| > shells I tried (zsh, bash, ash) exhibit such a problem.
| 
| It was originally discovered by people using some version of FreeBSD's
| /bin/sh.  I was able to reproduce it using the version of ash in
| Debian unstable.

Heck, I forgot config.status was re-execing itself when it doesn't
like the shell.  That's why I missed it I guess.

Thanks for the hint, I'm applying this:

Index: ChangeLog
from  Akim Demaille  <address@hidden>

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

Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.583
diff -u -u -r1.583 autoconf.texi
--- doc/autoconf.texi 5 Feb 2002 22:56:16 -0000 1.583
+++ doc/autoconf.texi 7 Feb 2002 09:44:45 -0000
@@ -8456,6 +8456,23 @@
 OK
 @end example
 
+Some shells, such as Ash 0.3.8, are confused by empty
address@hidden/@code{esac}:
+
address@hidden
+ash-0.3.8 $ @kbd{case foo in esac;}
address@hidden error: ";" unexpected (expecting ")")
address@hidden 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:
+
address@hidden
+$ @kbd{case foo in (foo) echo foo;; esac}
address@hidden error: `(' unexpected
address@hidden example
+
 
 @item @command{echo}
 @c -----------------