From: Eric Cooper <ecc@cmu.edu>
To: guile-user@gnu.org
Subject: Re: Guile continuations
Date: Sat, 22 Aug 2009 12:01:38 -0400 [thread overview]
Message-ID: <20090822160138.GA13497@localhost> (raw)
In-Reply-To: <3ae3aa420908220826r3eae4ce9p4f3502e5eba5de54@mail.gmail.com>
On Sat, Aug 22, 2009 at 10:26:40AM -0500, Linas Vepstas wrote:
> The wikipedia article on coroutines doesn't even link to a scheme
> version; the Wikipedia article on continuations could almost surely
> benefit from a cut-n-paste of your email.
>
> In fact, I'm planning on cut-n-pasting that into the talk page
> right now, if that's OK with you ...
Sure. I think this approach was first published here:
Haynes, C. T., Friedman, D. P., and Wand, M. 1984. Continuations
and coroutines. In Proceedings of the 1984 ACM Symposium on LISP
and Functional Programming (Austin, Texas, United States, August
06 - 08, 1984). LFP '84. ACM, New York, NY, 293-298.
--
Eric Cooper e c c @ c m u . e d u
prev parent reply other threads:[~2009-08-22 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 23:53 Guile continuations Linas Vepstas
2009-08-22 3:08 ` Eric Cooper
2009-08-22 15:26 ` Linas Vepstas
2009-08-22 16:01 ` Eric Cooper [this message]
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=20090822160138.GA13497@localhost \
--to=ecc@cmu.edu \
--cc=guile-user@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.
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).