From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15909 invoked by alias); 15 Feb 2014 22:56:48 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32391 Received: (qmail 29284 invoked from network); 15 Feb 2014 22:56:42 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140215145650.ZM2159@torch.brasslantern.com> Date: Sat, 15 Feb 2014 14:56:50 -0800 In-reply-to: <201402152219.s1FMJWZj027039@pws-pc.ntlworld.com> Comments: In reply to Peter Stephenson "Re: PATCH Re: zparseopts default associative array" (Feb 15, 10:19pm) References: <201402152219.s1FMJWZj027039@pws-pc.ntlworld.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: PATCH Re: zparseopts default associative array MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Feb 15, 10:19pm, Peter Stephenson wrote: } Subject: Re: PATCH Re: zparseopts default associative array } } Bart Schaefer wrote: } > I suspect I may have missed something with respect to multibyte and/or } > (un)metafication in zalloc_default_array()? } } I don't see why, since this is internal manipulation with any conversion } from input or to output formats occurring elsewhere (unless I'm missing } something, I haven't looked through the surrounding context with any care). Well, the array is going to end up with a mix of stuff copied directly from getarrvalue() and stuff copied from the argument linklist passed to bin_zparseopts(). It occured to me that those might not be in the same internal representation when not plain strings.