unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: The dynamic stack
Date: Wed, 7 Mar 2012 01:05:59 -0500	[thread overview]
Message-ID: <CA+U71=Nsqs_BrBOkunpRcShtVCroJp3Vs3v7jELoSrjFKKB3eQ@mail.gmail.com> (raw)
In-Reply-To: <87vcmh1nd2.fsf@pobox.com>

Hello,

>> The “dynwind stack” actually (I misread it the first time.)
>
> Yes, it did have this name before.  (More often, "the wind list".)  But
> since "dynwind" is overloaded so much (dynamic-wind operator, <dynwind>,
> scm_dynwind_*), and the dynamic stack can have other things on it like
> prompts, I thought it best to give it a new name.

I see your point about the old name, but I find the new name
confusing. What about the stack that holds regular program variables
and temporaries? That is also dynamic, so at first I thought you were
referring to that. I didn't know what was going on until this email.

I thought of "control stack", since the things on it deal with control
flow. But that is also confusing, because it doesn't include return
addresses and frame pointers.

Noah



  reply	other threads:[~2012-03-07  6:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 16:25 The dynamic stack Andy Wingo
2012-03-06 17:20 ` Ludovic Courtès
2012-03-06 20:32   ` Andy Wingo
2012-03-07  6:05     ` Noah Lavine [this message]
2012-03-07  9:51       ` Andy Wingo
2012-03-07 23:09     ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+U71=Nsqs_BrBOkunpRcShtVCroJp3Vs3v7jELoSrjFKKB3eQ@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=wingo@pobox.com \
    /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. 
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 read-only IMAP folder(s) and NNTP newsgroup(s).