On 2009-03-08 Alban browaeys <pra...@yahoo.com> wrote:
> >From \amethyst on freenode #bash (Neil Moore) :
> <\amethyst> it is a bug I think
> <\amethyst> that you still get the error even with $...@-foo}
> <\amethyst> but $...@+"$@"} probably shouldn't error out
> <\amethyst> since ${foo+bar} does not
> <\amethyst> or ${foo+"$foo"}
> I believe this should be cloned to bash (kept here too because the
> current $@ is to be fixed either way).
[...]
Hello,
I think I am going to drop set -u since I have got the feeling that
the decreased readability due the workarounds for $@ and $* outweighs
the benefit of set -u.
I still consider this upstream change a bad idea. There is a reason
why "$@" expands to nothing instead of an empty string if there are no
commandline args.
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
