From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: MAX_ARRLEN
Date: Mon, 23 Apr 2012 09:38:12 -0700 [thread overview]
Message-ID: <120423093812.ZM5059@torch.brasslantern.com> (raw)
In-Reply-To: <20120423162711.42a6bad1@pwslap01u.europe.root.pri>
On Apr 23, 4:27pm, Peter Stephenson wrote:
}
} 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.
I think something based on one of the process limits would be good.
Maybe combined with stashing it in a variable that can be modified.
Maybe even putting that variable in a module so it's not visible in a
barebones shell.
datasize, stacksize, and addressspace are all candidates for how to
figure out the limit. (Do we ever allocate arrays for zsh parameter
expansion on the stack?)
next prev parent reply other threads:[~2012-04-23 16:38 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 ` MAX_ARRLEN Mikael Magnusson
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 ` Bart Schaefer [this message]
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=120423093812.ZM5059@torch.brasslantern.com \
--to=schaefer@brasslantern.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).