From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-15004-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 26690 invoked from network); 20 Jun 2001 18:01:41 -0000
Received: from sunsite.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 20 Jun 2001 18:01:41 -0000
Received: (qmail 26388 invoked by alias); 20 Jun 2001 18:01:03 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 15004
Received: (qmail 26370 invoked from network); 20 Jun 2001 18:01:02 -0000
X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de)
Date: Wed, 20 Jun 2001 22:01:28 +0400 (MSD)
From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
X-X-Sender:  <bor@itsrm2.mow.siemens.ru>
To: Peter Stephenson <pws@csr.com>
cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: 4.1: multi-parameter for loop
In-Reply-To: <Tc0a88d015442f20480@mailsweeper01.cambridgesiliconradio.com>
Message-ID: <Pine.SV4.4.33.0106202158430.26619-100000@itsrm2.mow.siemens.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 20 Jun 2001, Peter Stephenson wrote:

>
> This extends the for syntax to take multiple parameters after it; they take
> multiple words from the argument list.  The main intended use of this is
> for imitating perl's `each' feature:
>
>   typeset -A assoc
>   assoc=(key1 val1 key2 val2)
>   for key value in ${(kv)assoc}; do
>     print $key $value
>   done
>

This for sure is incompatible with POSIX and all known shells. It does
not make legal scripts fail, but it makes illegal scripts legal. Should we
care about it?

-andrej