From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26761 invoked by alias); 23 Apr 2012 16:10:25 -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: 30446 Received: (qmail 2433 invoked from network); 23 Apr 2012 16:10:24 -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=fj20Y7MssNDH/o7ZMuRE/0xVI76egFEImlCn2+UuL4E=; b=KlxKU/7icWyWtqjPnvRtWJ55XL/y0uOCiM4UzW+2yhnZx8LdJQ1D1SN1yBhRzdNwpC Ib0WoOT1wcmEDiIgROeeiCpTQlTrV25K3dtxREs0OsBFM30xu0FTPAGQiOaxu1qjYrXn 4KTC495WlBZWOgN69mPynRBqNi1zRVDPfvQKJr10FCGd/4U3UYQvmqF+WJVwPkVpC68q JZgSUcfljphzhaaMeJZNKasrM4+aCe904NZJtMQaTfyClZPysSmbnYjoJ6EqXZYifd0b 6hseasoCi2OmQdEDhnKPICjJpVVAH/PJofvPx5T0+9P6Du3Jne1ApSalkQLwi0urPjP7 lS7g== MIME-Version: 1.0 In-Reply-To: <20120423162711.42a6bad1@pwslap01u.europe.root.pri> References: <20120423162711.42a6bad1@pwslap01u.europe.root.pri> Date: Mon, 23 Apr 2012 18:10:16 +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: > I've just hit MAX_ARRLEN. The array in question wasn't much larger than > the limit and when I commented out the checks everything just worked fine. > So it looks like an arbitrary limit isn't much use --- no great > surprise, I don't think anyone here is a big fan of them. > > What's the right thing to do? There are various grades ranging from > making it compilable out, through making it compile-time configurable > with an option to compile out, through making it an option to have the > check turned on, to having a variable that we check using getiparam() > each time, to having a special variable so that we don't need to get it > each time. I think the last option with a clearly named variable such > as ZSH_MAX_ARRAY_LENGTH that can be set to 0 to turn it off is probably > the best. http://www.zsh.org/mla/workers/2010/msg00013.html -- Mikael Magnusson