From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8762 invoked from network); 26 Jul 2001 09:58:16 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 26 Jul 2001 09:58:16 -0000 Received: (qmail 1419 invoked by alias); 26 Jul 2001 09:58:09 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15496 Received: (qmail 1408 invoked from network); 26 Jul 2001 09:58:08 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: Borsenkow Andrej To: Zsh hackers list Subject: RE: Nasty bug in array-element typeset assignments Date: Thu, 26 Jul 2001 13:57:58 +0400 Message-ID: <001f01c115b9$72dec660$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 > > 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. > > Yuk. Whoever decided on this has got a job on their hands. > Actually, I suspect it is a side effect of subscript quoting cleanup. I do not see any real changes in bin_typeset that are aimed at the above - but I suspect that 'foo[1]' was not treated as array subscript before. BTW it is allowed in 4.0.2, I do not have earlier versions here readily available. May be, it was always possible? -andrej