caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "T. Kurt Bond" <tkb@tkb.mpl.com>
To: Chet Murthy <chet@watson.ibm.com>
Cc: Dave Berry <dave@kal.com>,
	STARYNKEVITCH Basile <Basile.Starynkevitch@cea.fr>,
	caml-list@inria.fr
Subject: Re: callcc/cps-style programming
Date: Thu, 14 Dec 2000 14:20:53 -0500 (EST)	[thread overview]
Message-ID: <14905.7573.233207.196188@tkb.mpl.com> (raw)
In-Reply-To: <200012131636.LAA02306@bismarck-chet.watson.ibm.com>

Chet Murthy writes:
> I'm not saying that threads are bad.  Rather, what I'm saying is,
> there is little need, in a language like CAML, for _user-level_
> threads.  Kernel threads, you need, for talking to DB2 or Oracle.
> Period.  But user-level threads, implemented in the language, don't
> give you much value.  Much better to do some sort of explicit (perhaps
> semi-automated) CPS-conversion, and use an event-dispatcher.
> 
> Amongst other things, at least, you'll never have to worry about being
> time-sliced where you didn't expect it.


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.) 

http://x58.deja.com/=dnc/getdoc.xp?AN=622079764&CONTEXT=976821773.388825093&hitnum=0
http://www.ericsson.se/cslab/projects/etos.shtml
-- 
T. Kurt Bond, tkb@tkb.mpl.com



  reply	other threads:[~2000-12-15 12:51 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 [this message]
2000-12-15 13:31     ` Martin Berger
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=14905.7573.233207.196188@tkb.mpl.com \
    --to=tkb@tkb.mpl.com \
    --cc=Basile.Starynkevitch@cea.fr \
    --cc=caml-list@inria.fr \
    --cc=chet@watson.ibm.com \
    --cc=dave@kal.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).