zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: MAX_ARRLEN
Date: Tue, 24 Apr 2012 12:45:23 -0700	[thread overview]
Message-ID: <120424124523.ZM6747@torch.brasslantern.com> (raw)
In-Reply-To: <20120424143706.3ccc490d@pwslap01u.europe.root.pri>

On Apr 24,  2:37pm, Peter Stephenson wrote:
} 
} As something to do now, I'd be tempted either to "#if 0" the code until
} someone can come up with a replacement that is demonstrably useful, or
} implement $ZSH_MAX_ARRAY_LENGTH and initialise it to 0 (no limit),
} applying it at the current definitely non-optimal location.  Either
} option at least gives us something basic usable, which the current code
} isn't really.  Anything beyond that still seems to be somewhat
} ill-defined and I'd like finally to have something non-broken ASAP.

I'm OK with just removing the check entirely.  It's not like we don't
have other places where the shell might run out of memory.  This one
was just particularly egregious back in the day because you could eat
vast amounts of memory with what looked like an innocuous subscript
expression.  (I think the strange number for the limit was based on
the assumption that you were creating a mostly empty array. If we used
linked lists [ala bash] this would never come up.)


  reply	other threads:[~2012-04-24 19:45 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 ` MAX_ARRLEN Bart Schaefer
2012-04-24 13:37   ` MAX_ARRLEN Peter Stephenson
2012-04-24 19:45     ` Bart Schaefer [this message]
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=120424124523.ZM6747@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).