all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: alinsoar@voila.fr, emacs-devel@gnu.org
Subject: Re: stack size info
Date: Fri, 23 Mar 2007 11:01:32 -0400	[thread overview]
Message-ID: <E1HUlGm-0002eQ-LH@mail.agora-net.com> (raw)
In-Reply-To: <857it9m911.fsf@lola.goethe.zz> (message from David Kastrup on Thu, 22 Mar 2007 19:24:10 +0100)

   From: David Kastrup <dak@gnu.org>
   Date: Thu, 22 Mar 2007 19:24:10 +0100

   A Soare <alinsoar@voila.fr> writes:

   > STACKSIZE
   >      The maximum stack size this function needs. In case of recursion,
   >      every recursive call grows function's stack size with this constant.
   >
   > ########
   >
   > This is a litte better?

   I don't think so.  My guess is "The maximum stack size this function
   needs for execution, disregarding further (including recursive)
   function calls as those extend the stack on their own."

i'm inclined to leave the docs alone.  the node's entire context is a
single function and thus the STACKSIZE element of the byte-code function
object pertains to a single function call.

however, if pressed, i will suggest:
The maximum stack size this function might need when called.

"might" because it is possible that any particular call uses less than
that amount.  "when called" addresses recursion.

is that wording ok?

thi

  reply	other threads:[~2007-03-23 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 15:19 stack size info A Soare
2007-03-22 18:24 ` David Kastrup
2007-03-23 15:01   ` Thien-Thi Nguyen [this message]
2007-03-23 16:00     ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2007-03-26 10:42 A Soare
2007-03-23 15:08 A Soare
2007-03-24 13:38 ` Thien-Thi Nguyen
2007-03-20 13:22 A Soare
2007-03-20 16:14 ` ttn

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=E1HUlGm-0002eQ-LH@mail.agora-net.com \
    --to=ttn@gnuvola.org \
    --cc=alinsoar@voila.fr \
    --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.