From: Bhanu Nagendra Pisupati <bpisupat@cs.indiana.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Non-stack-based calling conventions
Date: Mon, 18 Feb 2008 17:56:15 -0500 [thread overview]
Message-ID: <Pine.GSO.4.58.0802181737160.22332@school.cs.indiana.edu> (raw)
In-Reply-To: <20080218221815.1CC1E1F11C@mail.cse.psu.edu>
> Maybe someone in this list can provide a good example of coroutines
> use?
For a neat illustration (and critique) of coroutines lookup:
"Experimenting with tail-recursion and simulating coroutines" -
http://doi.acm.org/10.1145/306286.306315
For those with a bent toward functional programming, there are
similarities with the trampolined style:
"Trampolined style" -
http://doi.acm.org/10.1145/317765.317779
Thanks,
-Bhanu
parent reply other threads:[~2008-02-18 22:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20080218221815.1CC1E1F11C@mail.cse.psu.edu>]
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=Pine.GSO.4.58.0802181737160.22332@school.cs.indiana.edu \
--to=bpisupat@cs.indiana.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).