From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: stack overflow limit
Date: Wed, 4 May 2011 10:04:40 -0700 [thread overview]
Message-ID: <62EAF87B4F294B2FB9F2ED7EC6E562D0@us.oracle.com> (raw)
Not a request or a suggestion. I'm just wondering about the stack size limit
(e.g. for regexp search, search.c).
Would it make sense to make it any bigger, given that machines nowadays are more
powerful and have more memory, or do you consider that pretty much all such
stack overflows (e.g. for regexp matching) are just due to poorly chosen
regexps?
Again, just wondering if it might be appropriate (time) to bump the stack limit.
(No, I don't have a particular use case or regexp in mind.)
next reply other threads:[~2011-05-04 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 17:04 Drew Adams [this message]
2011-05-04 18:51 ` stack overflow limit Stefan Monnier
2011-05-04 20:43 ` Eli Zaretskii
2011-05-05 7:16 ` Andy Wingo
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=62EAF87B4F294B2FB9F2ED7EC6E562D0@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.