From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-35525-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 14138 invoked by alias); 19 Jun 2015 14:16:38 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 35525
Received: (qmail 7732 invoked from network); 19 Jun 2015 14:16:35 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS autolearn=ham
	autolearn_force=no version=3.4.0
X-AuditID: cbfec7f5-f794b6d000001495-20-558421e41546
Date: Fri, 19 Jun 2015 15:06:24 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: Typeset with array
Message-id: <20150619150624.3368cd00@pwslap01u.europe.root.pri>
In-reply-to: <20150619123930.2688d9e3@pwslap01u.europe.root.pri>
References: <5578996E.3080700@thequod.de>
 <150610191427.ZM30841@torch.brasslantern.com> <5579C247.1060800@thequod.de>
 <150611183639.ZM32247@torch.brasslantern.com>
 <20150612094237.338f79d5@pwslap01u.europe.root.pri>
 <20150619123930.2688d9e3@pwslap01u.europe.root.pri>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsVy+t/xq7pPFFtCDe5vZ7I42PyQyYHRY9XB
	D0wBjFFcNimpOZllqUX6dglcGf1Pu5kLnnNUdD2+xtTA+JWti5GTQ0LAROLYrW8sELaYxIV7
	64HiXBxCAksZJd4ue8oO4cxgkpj1op8RwtnGKHF8yiwmkBYWAVWJC69Os4PYbAKGElM3zQYq
	4uAQEdCWaP8oBhIWFpCX2H1yPzNImFfAXmLHBEmQMKeAg8TL1wuhlk1mknjV9hfsCn4BfYmr
	fz8xQVxkLzHzyhlGEJtXQFDix+R7YDXMAloSm7c1sULY8hKb17xlBrGFBNQlbtzdzT6BUWgW
	kpZZSFpmIWlZwMi8ilE0tTS5oDgpPddIrzgxt7g0L10vOT93EyMkaL/uYFx6zOoQowAHoxIP
	r8G35lAh1sSy4srcQ4wSHMxKIrwFCi2hQrwpiZVVqUX58UWlOanFhxilOViUxHln7nofIiSQ
	nliSmp2aWpBaBJNl4uCUamAsbeLM+Ttvj492yYvXgrqeZy5dOuq57EXaXOnw1QffRGbFbnnH
	zRt8rnRjckGOWfPdZ3+ypl2ZV9D9YtLTs3t5zU1cd0w8HaQTp9X5a63mwUePr5wSn51bZLZh
	eZ/qkx+6tyPE3rKou4XxPgv4bfrjmPvhfVtWJLHd+TBPklk8cr73HeY3E14cUWIpzkg01GIu
	Kk4EAF1NpGlWAgAA

On Fri, 19 Jun 2015 12:39:30 +0100
Peter Stephenson <p.stephenson@samsung.com> wrote:
> I've got as far as a successful
> 
> % typeset array=(one two buckle my shoe)
> % print -l $array
> one
> two
> buckle
> my
> shoe
> 
> but there's a lot more debugging and testing to do.
> 
> This is on a branch typeset-array, which I'll push so you can have a
> look.

Pushed.  Fairly stable, but a couple of tests failing:

- I haven't implemented XTRACE yet.  Will follow.

- The new interface "fixes" the old behaviour

  typeset noktfoo=`echo noktarg1 noktarg2`

so that this now assigns a scalar to noktfoo with no wordsplitting.
This is certainly correct for the interface we are trying to implement,
because it's what bash does.  However, it was previously controlled by
KSH_TYPESET.  What's the right way to do it from now on?  I can probably
kludge in the old behaviour with NO_KSH_TYPESET if it seems desirable,
though logically that shouldn't really control the reserved word
interface which should parse consistently.

Anyway, I haven't touched that test case for nokshtypeset yet.

pws