From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: zsh-3.1.5-pws-7: "$a[@]" with $a unset
Date: Fri, 12 Feb 1999 16:45:38 +0100 [thread overview]
Message-ID: <9902121545.AA44295@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Fri, 12 Feb 1999 07:43:45 NFT." <990212074345.ZM8144@candle.brasslantern.com>
> } Sven Wischnowsky wrote:
> } > % foo() { echo $# }
> } > % unset a
> } > % foo $a[@]
> } > 0 # fine
> } > % foo "$a[@]"
> } > 1 # oops
>
> That's not an "oops". That's the way it's supposed to work. Try the
> equivalent code in bash.
Bash doesn't even have arrays, apart from "$@", of course. Try it in
ksh, and remember you need "${f[@]}" because the bracing rules are
more strict, and you'll find it elides the whole thing as with the
patch.
Taking a @ subscript was never a well-defined thing to do on a scalar,
whether or not it happens to be so with a zsh extension; its essential
purpose is to provide word splitting for arrays in strings, so zero
elements gives zero words. (And if it leaves a null argument on the
line for an empty scalar, I would argue that's inconsistently
implemented.)
> I don't think we want this patch.
It seems pretty clear to me the shell is just plain broken without it.
--
Peter Stephenson <pws@ibmth.df.unipi.it> Tel: +39 050 844536
WWW: http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy
next prev parent reply other threads:[~1999-02-12 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-12 8:53 Tar file and Re: Bad interaction between -iprefix and -string Sven Wischnowsky
1999-02-12 9:28 ` PATCH: zsh-3.1.5-pws-7: "$a[@]" with $a unset Peter Stephenson
1999-02-12 15:43 ` Bart Schaefer
1999-02-12 15:45 ` Peter Stephenson [this message]
1999-02-12 17:33 ` Bart Schaefer
1999-02-13 7:05 ` PATCH: " Bart Schaefer
1999-02-12 9:48 Sven Wischnowsky
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=9902121545.AA44295@ibmth.df.unipi.it \
--to=pws@ibmth.df.unipi.it \
--cc=zsh-workers@sunsite.auc.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).