mirror of
git://git.sv.gnu.org/autoconf
synced 2025-02-23 14:09:51 +08:00
* doc/autoconf.texi (Limitations of Builtins): More about
case/esac.
This commit is contained in:
parent
d03ab7023b
commit
486b91d289
@ -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
|
||||
|
@ -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 -----------------
|
||||
|
Loading…
Reference in New Issue
Block a user