From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: set -A
Date: Fri, 07 Feb 2003 10:48:12 +0000 [thread overview]
Message-ID: <12330.1044614892@csr.com> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Fri, 07 Feb 2003 03:53:14 GMT." <1030207035314.ZM24755@candle.brasslantern.com>
"Bart Schaefer" wrote:
> On Feb 6, 7:01pm, Paul Ackersviller wrote:
> } Subject: set -A
> }
> } unset arr
> } set -A arr "${arr[@]}" first
> } [ ${#arr[@]} = 2 ] && echo "arr[0]='${arr[0]}' arr[1]='${arr[1]}'"
> }
> } Note the null entry on the start of the array.
>
> This really has nothing to do with "set -A".
>
> If you've unset arr, then arr is not an array, and hence ${arr[@]} is
> not an array either, and therefore "${arr[@]}" does not behave like
> an array; rather, it behaves like a string, so putting it in double
> quotes yields the empty string.
But the `@' subscript is not documented to do anything useful for
strings, nor can I see why anyone would assume it was useful in that
case, nor, if they *did* think, that why they would assume that it
produced a null string instead of the usual elision of the argument. (I
haven't put that very well.)
I think we could safely and consistently have a non-existent parameter
treated as an array in this special case without any negative impact.
The main problem with doing anything is that this part of the code is
particularly ghastly and I shudder at going anywhere near it.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next prev parent reply other threads:[~2003-02-07 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 0:01 Paul Ackersviller
2003-02-07 3:53 ` Bart Schaefer
2003-02-07 10:48 ` Peter Stephenson [this message]
2003-02-07 16:48 ` Bart Schaefer
2003-02-07 17:36 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12330.1044614892@csr.com \
--to=pws@csr.com \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).