caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Martin Berger <martinb@dcs.qmw.ac.uk>
To: "T. Kurt Bond" <tkb@tkb.mpl.com>, caml-list@inria.fr
Subject: Re: callcc/cps-style programming
Date: Fri, 15 Dec 2000 13:31:04 +0000	[thread overview]
Message-ID: <3A3A1D18.8EB69865@dcs.qmw.ac.uk> (raw)
In-Reply-To: <14905.7573.233207.196188@tkb.mpl.com>

"T. Kurt Bond" wrote:

> Hmmm.  Well, try telling the Erlang folks that super-lightweight
> user-level processes aren't useful.  Or the Gambit Scheme folks: their
> next release has lightweight threads built on call/cc.  (Note: these
> two things may be related.)

concerning lightweight threads and continuations, simon peyton-jones
and norman ramsey have a nice paper:

	http://www.cminusminus.org/abstracts/c--con.html

and then there's always mitch wand's classic "Continuation-Based Multiprocessing",
available from:

	http://www.ccs.neu.edu/home/wand/pubs.html

regarding the merits of using threads vs callback, i agree that
there are few working programmers who can be trusted with concurrency,
but well-designed multi-threaded programms tend to be easier to
understand. it comes down to education really. of course there are
also various performance trade-offs.


martin



  reply	other threads:[~2000-12-15 16:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 13:44 Dave Berry
2000-12-13 16:36 ` Chet Murthy
2000-12-14 19:20   ` T. Kurt Bond
2000-12-15 13:31     ` Martin Berger [this message]
2000-12-15 18:37   ` Julian Assange
2000-12-15 23:10     ` Chet Murthy
  -- strict thread matches above, loose matches on Subject: below --
2000-12-14 19:08 forsyth
2000-12-06 20:13 Joe Lisp
2000-12-07  8:31 ` STARYNKEVITCH Basile
2000-12-09  3:58   ` eijiro_sumii
2000-12-09 18:48   ` Chet Murthy
2000-12-12 17:14     ` John Max Skaller
2000-12-08 10:50 ` Xavier Leroy

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=3A3A1D18.8EB69865@dcs.qmw.ac.uk \
    --to=martinb@dcs.qmw.ac.uk \
    --cc=caml-list@inria.fr \
    --cc=tkb@tkb.mpl.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 NNTP newsgroup(s).