From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <Peter.Stephenson@csr.com>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: MAX_ARRLEN
Date: Mon, 23 Apr 2012 18:10:16 +0200 [thread overview]
Message-ID: <CAHYJk3Qxx3nLLMARiGgbo9U8KL3NaOXO2ioWPA3n=6sJmmMzRQ@mail.gmail.com> (raw)
In-Reply-To: <20120423162711.42a6bad1@pwslap01u.europe.root.pri>
On 2012-04-23, Peter Stephenson <Peter.Stephenson@csr.com> 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
next prev parent reply other threads:[~2012-04-23 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 15:27 MAX_ARRLEN Peter Stephenson
2012-04-23 16:10 ` Mikael Magnusson [this message]
2012-04-23 16:21 ` MAX_ARRLEN Bart Schaefer
2012-04-23 16:27 ` MAX_ARRLEN Peter Stephenson
2012-04-23 16:36 ` MAX_ARRLEN Mikael Magnusson
2012-04-23 16:40 ` MAX_ARRLEN Peter Stephenson
2012-04-23 16:45 ` MAX_ARRLEN Mikael Magnusson
2012-04-23 16:38 ` MAX_ARRLEN Bart Schaefer
2012-04-24 13:37 ` MAX_ARRLEN Peter Stephenson
2012-04-24 19:45 ` MAX_ARRLEN Bart Schaefer
2012-04-25 9:01 ` MAX_ARRLEN Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHYJk3Qxx3nLLMARiGgbo9U8KL3NaOXO2ioWPA3n=6sJmmMzRQ@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=Peter.Stephenson@csr.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).