Bug #6756
closed
sh (and ksh) have issues with ${1+"$@"}
100%
Description
as noticed during libtool gnulib testing, sh and ksh have issues with a particular construct as
discussed in problem report raised by Bob Friesenhahn:
http://thread.gmane.org/gmane.comp.sysutils.autoconf.bugs/8814
There seems to be a long history of issues most everywhere with this, as noted
https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Shell-Substitutions.html
and, for instance,
http://www.in-ulm.de/~mascheck/various/bourne_args/
perhaps time, if not to upgrade to a more recent ast-ksh, to at least fix this "workaround" feature as expected.
Related issues
Updated by Richard PALO about 7 years ago
I can confirm that a more ast-ksh, the following being in pkgsrc,
version sh (AT&T Research) 93u+ 2012-08-01
seems to work fine on this front.
Updated by Andy Fiddaman about 2 years ago
- Related to Feature #13405: ksh93 update to 2012-08-01 added
Updated by Electric Monk about 2 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
git commit b30d193948be5a7794d7ae3ba0ed9c2f72c88e0f
commit b30d193948be5a7794d7ae3ba0ed9c2f72c88e0f
Author: Andy Fiddaman <omnios@citrus-it.co.uk>
Date: 2021-01-30T17:13:33.000Z
13405 ksh93 update to 2012-08-01
13434 sh: mishandles backslash as last character of a block of input
11750 ksh mkdir builtin doesn't honor special file permissions
9199 ksh93 builtin *grep -v mishandles blank lines, blows up libgcrypt-config
6756 sh (and ksh) have issues with ${1+"$@"}
6520 ksh: sleep could wait forever
4860 ksh93: core in printf
3791 /bin/sh's builtin 'rm' busted: 'rm -f' without arguments returns error
1047 ksh overwrites child core files
880 ksh93 coredumps on 'unset'
499 "interrupted system call" when using "tee" builtin in ksh
Reviewed by: Robert Mustacchi <rm@fingolfin.org>
Reviewed by: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
Reviewed by: Dominik Hassler <hadfl@omnios.org>
Approved by: Rich Lowe <richlowe@richlowe.net>