From: Brian Rogoff <bpr@bpr.best.vwh.net>
To: bcpierce@cis.upenn.edu
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Continuations -- summary of replies
Date: Mon, 8 Apr 2002 03:29:15 +0000 (GMT) [thread overview]
Message-ID: <Pine.BSF.4.40.0204080314451.75656-100000@bpr.best.vwh.net> (raw)
In-Reply-To: <9207.1018099816@saul.cis.upenn.edu>
Thanks for the summary! A practically oriented page of cool continuation
tricks would be a very useful thing.
Lloyd Allison, who wrote an excellent, short introduction to denotational
semantics, has a few papers on practical uses of continuation passing
style, including one in Java (!) I think.
L.Allison. Continuations implement generators and streams.
Computer Journal 33(5) 460-465 1990
L. Allison, Generator and search objects in Java.
J J. Res. and Practice in Inf. Tech.
Some of the papers are available here
http://www.csse.monash.edu.au/~lloyd/Paperz.shtml
I'm a bit surprised by this comment from Olivier Danvy
> Let me conclude with a plea: despite IT technologies, BTA analysis, Meta
> ML, etc., let us resist to CPS style, OK?
I guess he's saying that we shouldn't write CPS style code (I can't say
for sure), but I find some of the nice CPS examples (like his
functional unparsing one) really compelling. Oh well, I'll still be
anxiously awaiting those lecture notes.
-- Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-04-08 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 13:30 Benjamin C. Pierce
2002-04-08 3:29 ` Brian Rogoff [this message]
2002-04-08 14:17 ` Zhe Yang
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.BSF.4.40.0204080314451.75656-100000@bpr.best.vwh.net \
--to=bpr@bpr.best.vwh.net \
--cc=bcpierce@cis.upenn.edu \
--cc=caml-list@pauillac.inria.fr \
/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).