[prev] [thread] [next] [lurker] [Date index for 2006/12/19]
> Why-oh-why are vile constructs like ${1+"$@"} still being used?
$@ is so hateful I don't see why they bothered trying to make it even
minutely less so without actually fixing it.
$ set a b c
$ echo "build/$@.c"
build/a b c.c
In what circumstance is that *ever* desirable? At least when you needed to
do ${1+"$@"} it made sense that "foo$@bar" was broken. But for the love of god
at least make it:
$ set a b c
$ echo "build/$@.c"
build/a.c build/b.c build/c.c
THAT would actually make sense, and make "$@" a special case of a general rule.
I use ${1+"$@"} so that I never ever forget that they didn't actualy make
"$@" behave logically... they just rang more changes on the parable of the
echo.
There's stuff above here
Generated at 03:01 on 20 Dec 2006 by mariachi 0.52