From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2487 invoked by alias); 23 Apr 2012 16:36:28 -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: 30449 Received: (qmail 14482 invoked from network); 23 Apr 2012 16:36:27 -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.6 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_LOW, T_DKIM_INVALID autolearn=no version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.160.43 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=X8NRhtA+V1C+/4KAJa1nfp4Q2qLBKHhNkckcabWUGBs=; b=h3O1vWq1qgQ3ZV4KLH+h+HLeI34TdlO6IPA4oL7Fm/FL1iOeQZtHZ54FPUJ9zTf17S Zyue3V1q8/46NzSDvrrmVUrX8HmEsD8BB1+ABJvkZTnQobBRDvQaEK4VfucRGZkZd3hB okqSV/r2UZGJBq5KZWQkmu/nol9zfArJGZeBFT1ZVZZUy37d/1bUgb84a2AK1i58ZdkH n8HPqjHiMFT4dojcYFA5hjEw3JfuS+6UmxmZUrhN4ZuJRYO7jnWAAbA0Dc4EKr9xaT2r xWCTFTfDJGBAKld/Naw/mBb5/oUsjhlrbupZm7cs+OOf5esR0w0+aa7p7OzE6BFQpTDx YMJQ== MIME-Version: 1.0 In-Reply-To: <20120423172723.238137e1@pwslap01u.europe.root.pri> References: <20120423162711.42a6bad1@pwslap01u.europe.root.pri> <120423092123.ZM5041@torch.brasslantern.com> <20120423172723.238137e1@pwslap01u.europe.root.pri> Date: Mon, 23 Apr 2012 18:36:22 +0200 Message-ID: Subject: Re: MAX_ARRLEN From: Mikael Magnusson To: Peter Stephenson Cc: "Zsh Hackers' List" Content-Type: text/plain; charset=UTF-8 On 2012-04-23, Peter Stephenson wrote: > On Mon, 23 Apr 2012 09:21:23 -0700 > Bart Schaefer wrote: >> On Apr 23, 6:10pm, Mikael Magnusson wrote: >> } >> } http://www.zsh.org/mla/workers/2010/msg00013.html >> >> And >> >> http://www.zsh.org/mla/workers/2010/msg00015.html > > Those are basically saying yes, the current set up has problems but we'd > quite like something. Hence my immediate suggestions of what we > *actually* do. > > The only additional matter arising is that it appears quite a lot of > people would be happy with the limit defaulting off. I replied with the link because you didn't refer to the previous discussion at all, so I wasn't sure if you remembered it :). The problem with the current approach is that it only limits accessing an array beyond a certain index, even if it's already larger, and you can create arrays of any size by other means. To me it seems like the limit is applied in the wrong place at least. If there are places that unexpectedly create large arrays, we should add the safeguards in those places, if possible. -- Mikael Magnusson