From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9952 invoked from network); 26 Jul 2001 10:04:36 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 26 Jul 2001 10:04:36 -0000 Received: (qmail 2987 invoked by alias); 26 Jul 2001 10:04:29 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15497 Received: (qmail 2976 invoked from network); 26 Jul 2001 10:04:28 -0000 Sender: kiddleo Message-ID: <3B5FEB29.884D31BF@u.genie.co.uk> Date: Thu, 26 Jul 2001 11:04:25 +0100 From: Oliver Kiddle X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Zsh hackers list Subject: Re: Nasty bug in array-element typeset assignments References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Peter Stephenson wrote: > > Borsenkow Andrej wrote: > > > "Bart Schaefer" wrote: > > > > local 'foo[1]'=X > > > > > > Is this supposed to be supported? I certainly haven't done anything about > > > it. > > > > > > > Yes, recent changes has enabled it. Really? So what would it do? Make the whole foo array local or just the first element? Clearly neither works. > Yuk. Whoever decided on this has got a job on their hands. > Typeset is going to get *very* confused. Each change like this multiplies, I'd say that it already is very confused. I haven't had time for a couple of weeks now but last time I looked at the nameref stuff, that code was doing my head in. However, I wouldnt have thought it'd be too hard to get it to print an error message for the above case. Oliver