From: Rich Neswold <rich.neswold@gmail.com>
To: caml-list@yquem.inria.fr
Cc: Romain Beauxis <toots@rastageeks.org>
Subject: CML Discussion (was: Smart ways to implement worker threads)
Date: Thu, 15 Jul 2010 12:50:30 -0500 [thread overview]
Message-ID: <AANLkTin6KxM9av6euRjj4_loQ76LtpuhmYTzEpbmLaPu@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
On Thu, Jul 15, 2010 at 11:19 AM, David McClain <
dbm@refined-audiometrics.com> wrote:
> That is not the same as OCaml's architecture, and so OCaml can implement
> about 90% of CML but that last 10% might kill your dreams. CML likes to
> spawn potential handlers, of which only one will get the go ahead. The
> others are expected to die, after possibly cleaning up state.
>
So which 10% of the Event module is poorly implemented? Or is it that the
Event module doesn't have a spawn function and relies on the Thread module?
Is it fixable (could a CML module be created for OCaml that faithfully
implements the run-time described in Reppy's book)?
I thought I read some details, recently, which described CML threads
implemented as continuations rather than system threads, which made them
inexpensive (relative to OS threads) to create. I'll have to go through my
blog lists to see where I read that.
Thanks for your insights!
--
Rich
Google Reader: https://www.google.com/reader/shared/rich.neswold
Jabber ID: rich@neswold.homeunix.net
[-- Attachment #2: Type: text/html, Size: 1690 bytes --]
next reply other threads:[~2010-07-15 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 17:50 Rich Neswold [this message]
2010-07-15 18:24 ` [Caml-list] " David McClain
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=AANLkTin6KxM9av6euRjj4_loQ76LtpuhmYTzEpbmLaPu@mail.gmail.com \
--to=rich.neswold@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=toots@rastageeks.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