From: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
Cc: caml-list@inria.fr
Subject: [Caml-list] Continuations: an implementation
Date: Sun, 15 Dec 2002 17:06:59 +0000 [thread overview]
Message-ID: <3DFCB6B3.70608@univ-savoie.fr> (raw)
In-Reply-To: <87bs3rlr7q.fsf@ketanu.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 2826 bytes --]
Here is an implementation of callcc for OCaml using fork.
The only problems are:
- I did not test it (but it should work)
- The limited number of fork calls
Note: the implementation of fork on Linux, makes a minimum of page copying, so
it should be reasonably fast
-- callcc.mli --
(* callcc fn: standard callcc, uses exit code 3 for internal use. *)
val callcc : (('a -> 'b) -> 'a) -> 'a
----------------
-- callcc.ml ---
open Unix
open Sys
let all_signals = [
sigabrt; (* Abnormal termination *)
sigalrm; (* Timeout *)
sigfpe; (* Arithmetic exception *)
sighup; (* Hangup on controlling terminal *)
sigill; (* In id hardware instruction *)
sigint; (* Interactive interrupt (ctrl-C) *)
sigkill; (* Termination (cannot be ignored) *)
sigpipe; (* Broken pipe *)
sigquit; (* Interactive termination *)
sigsegv; (* In id memory reference *)
sigterm; (* Termination *)
sigusr1; (* Application-defined signal 1 *)
sigusr2; (* Application-defined signal 2 *)
(* sigchld; Child process terminated, do not ignore that one !*)
sigcont; (* Continue *)
sigstop; (* Stop *)
sigtstp; (* Interactive stop *)
sigttin; (* Terminal read from background process *)
sigttou; (* Terminal write from background process *)
sigvtalrm; (* Timeout in virtual time *)
sigprof (* Profiling interrupt *)
]
let ignore_all_signals () =
let previous = List.map (fun s -> try signal s Signal_ignore with Sys_error
_ -> Signal_ignore) all_signals in
fun () ->
List.iter2 (fun s b -> try set_signal s b with Sys_error _ -> ())
all_signals previous
let callcc (fn : ('a -> 'b) -> 'a) =
let filename = Filename.temp_file "callcc" "val" in
let gn (x : 'a) =
let ch = open_out filename in
Marshal.to_channel ch x [Marshal.Closures];
close_out ch;
exit 3
in
let restore_signals = ignore_all_signals () in
let pid = fork () in
if pid = 0 then begin
restore_signals ();
fn gn
end else
let rec kn pid =
match waitpid [] pid with
_, WEXITED 3 ->
let ch = open_in filename in
let r = Marshal.from_channel ch in
close_in ch;
remove filename;
let pid = fork () in
if pid = 0 then (restore_signals (); r) else kn pid
| _, WEXITED n -> exit n
| _, _ -> exit 1
in kn pid
----------------
--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex
tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature
---------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2002-12-15 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 18:49 [Caml-list] Continuations Ceri Storey
2002-12-11 1:43 ` [Caml-list] Site down Eric Merritt
2002-12-11 9:19 ` [Caml-list] Continuations Christophe Raffalli
2002-12-12 5:51 ` [Caml-list] Continuations Michaël Grünewald
2002-12-15 17:06 ` Christophe Raffalli [this message]
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=3DFCB6B3.70608@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--cc=caml-list@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