zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Empty [(I)...] subscripting of assoc arrays (was Re: PATCH: completion)
Date: Wed, 25 Aug 1999 15:14:22 +0000	[thread overview]
Message-ID: <990825151422.ZM24565@candle.brasslantern.com> (raw)
In-Reply-To: <199908231200.OAA03141@beta.informatik.hu-berlin.de>

I think we now have entirely too many topics going on that all have the
subject "Re: PATCH: completion".

On Aug 23,  2:00pm, Sven Wischnowsky wrote:
} Subject: Re: PATCH: completion
}
} > This is because "-a" in compadd arguments. It is the result of
} > expansion of "dopts[${(@)^dopts[(I)${ws[1][1]}[$uns]]}]" and
} > "odopts[${(@)^odopts[(I)${ws[1][1]}[$uns]]}]".
} 
} Ah, sorry, I didn't test it with `[(I)...]'. So I think this is a real 
} bug, to be fixed in C. I'd like to hear Bart about this, though,
} because there was explicit code to turn empty array-subscripts into
} non-arrays. Maybe the effect this had on associations subscripted with 
} `[(I)...]' and `[(R)...]' was pure oversight, though.

It was oversight in that I didn't consider it; but either the patch you
sent is correct or else it's going to cause a core dump at subst.c:1713 

	    i = 1;
	    /* aval[1] is non-null here */
	    while (aval[i + 1]) {

in some circumstances that I'm not able to predict offhand.  I tend to
think it'll be OK.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1999-08-25 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-23 12:00 PATCH: completion Sven Wischnowsky
1999-08-25 15:14 ` Bart Schaefer [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=990825151422.ZM24565@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).