all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Herbert Euler" <herberteuler@hotmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Max-specpdl-size Bug in Emacs Lisp Interpreter?
Date: Wed, 19 Apr 2006 13:11:13 +0800	[thread overview]
Message-ID: <BAY112-F193146070659F4D4F0B903DAC50@phx.gbl> (raw)
In-Reply-To: <200604190403.k3J43PI3010087@jane.dms.auburn.edu>

>From: Luc Teirlinck <teirllm@dms.auburn.edu>
>To: herberteuler@hotmail.com
>CC: emacs-devel@gnu.org, miles@gnu.org
>Subject: Re: Max-specpdl-size Bug in Emacs Lisp Interpreter?
>Date: Tue, 18 Apr 2006 23:03:25 -0500 (CDT)
>
>Guanpeng Xu wrote:
>
>    I agree.  I think it would be better if this information appears
>    not only in elisp manual, but also in docstring of
>    'max-specpdl-size' as well, if the increment cannot be avoided.
>
>I now see that with "this information" you meant that entry to the
>Lisp debugger increases the value.  It would do no harm to mention
>this it the docstring.  However, I believe that the current docstring
>already makes clear that `max-specpdl-size' is no hard limit.

If you mean "However, if you increase it too far, Emacs could run
out of memory trying to make the stack bigger." make "no hard
limit" clear, I don't agree.  Who will know what the connection
between 'max-specpdl-size' and stack is without reading source
and/or without reading elisp manual?  Perhaps even reading elisp
manual is insufficient.

Regards,
Guanpeng Xu

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

  reply	other threads:[~2006-04-19  5:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-16  7:59 Max-specpdl-size Bug in Emacs Lisp Interpreter? Herbert Euler
2006-04-17  2:40 ` Herbert Euler
2006-04-17  9:06   ` Romain Francoise
2006-04-18  1:41   ` Richard Stallman
2006-04-18  3:20     ` Herbert Euler
2006-04-18  6:36       ` David Kastrup
2006-04-18 14:07         ` Herbert Euler
2006-04-18 11:25       ` Juanma Barranquero
2006-04-18 20:50       ` Richard Stallman
2006-04-19  1:43         ` Herbert Euler
2006-04-17 17:56 ` Richard Stallman
2006-04-18  2:18   ` Herbert Euler
2006-04-18  2:22     ` Miles Bader
2006-04-18  5:44       ` Luc Teirlinck
2006-04-18 20:50         ` Richard Stallman
2006-04-18 23:34           ` Miles Bader
2006-04-18 23:43             ` David Kastrup
2006-04-19  3:07               ` Herbert Euler
2006-04-19 15:40                 ` Richard Stallman
2006-04-19  2:59             ` Herbert Euler
2006-04-19  3:47               ` Luc Teirlinck
2006-04-19  4:03               ` Luc Teirlinck
2006-04-19  5:11                 ` Herbert Euler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-18 13:51 Herbert Euler
2006-04-15  8:24 Herbert Euler

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=BAY112-F193146070659F4D4F0B903DAC50@phx.gbl \
    --to=herberteuler@hotmail.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.