From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: CallCC using fork (and garbage collected processes)
Date: Mon, 16 Jul 2007 06:30:22 +0100 [thread overview]
Message-ID: <200707160630.23737.jon@ffconsultancy.com> (raw)
Just another crazy idea. So Oleg's callcc for OCaml works by copying the OCaml
bytecode stack and its rather nifty because you can trivially control invert
parsers and so forth.
You can replicate the native-code stack using fork. What if you wrap the
forked process in an object and set the finalizer to pass it a message
telling it to die. Then you could invoke the process (continuation) to
propagate computation. Maybe you can pass your child the pipe from your
parent so that it can respond directly and then die yourself (a tail call!).
I know this is really silly because you've got the OCaml GC collecting
processes (which is even worse than GCing OpenGL textures) but my machine can
fork processes pretty quickly and I'm just wondering if anyone's tried it?
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
The OCaml Journal
http://www.ffconsultancy.com/products/ocaml_journal/?e
next reply other threads:[~2007-07-16 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 5:30 Jon Harrop [this message]
2007-07-16 6:07 ` [Caml-list] " skaller
2007-07-16 16:46 ` Richard Jones
2007-07-16 17:25 ` skaller
2007-07-16 17:57 ` Tom
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=200707160630.23737.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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).