zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] ksh_zero_subscript messes with associative arrays
Date: Wed, 27 Jul 2022 09:21:56 +0100 (BST)	[thread overview]
Message-ID: <1689193830.64958.1658910116770@mail.virginmedia.com> (raw)
In-Reply-To: <CAH+w=7ZrRcowAJooO-bWeM=OPZ9P=9a2fxD1L_vBRKs=wvX5GQ@mail.gmail.com>

> On 26/07/2022 18:10 Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Tue, Jul 26, 2022 at 10:00 AM Bart Schaefer
> <schaefer@brasslantern.com> wrote:
> >
> > Something is tickling my brain to the effect that this was left this
> > way for bug-compatibility with some version of (perhaps pd) ksh ...
> 
> More of this comes back to me ... I think the situation is/was this:
> 
> hash=( [Y]=why [0]=zero )
> echo $hash
> zero
> 
> That is, reference to the entire hash without subscript returns a
> reference to the element with key "0", just as reference to an array
> without subscript returns the 0th element.
> 
> So there's probably not after all a connection to other unset
> elements, but I think PWS's patch will alter the above behavior as
> well?

Yes, I remember this oddity now.

However, "echo $hash" with only kshzerosubscript (not ksharrays ---
with which it would be pointless) echoes the full hash, so no
change here.  But I suspect there are other cases it does affect.

Do we actually care?  Could we just document it?  Or is the effect
so small anyway it's best to leave it the way it is and note the
oddities with hashes?

pws


      reply	other threads:[~2022-07-27  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 16:18 Felipe Contreras
2022-07-26 16:32 ` Peter Stephenson
2022-07-26 17:00   ` Bart Schaefer
2022-07-26 17:10     ` Bart Schaefer
2022-07-27  8:21       ` Peter Stephenson [this message]

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=1689193830.64958.1658910116770@mail.virginmedia.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.org \
    /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).