From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: discussion: serialize procedures and continuations
Date: Sat, 17 Aug 2013 14:55:36 +0200 [thread overview]
Message-ID: <87li40xyrb.fsf@gnu.org> (raw)
In-Reply-To: CAGyY8NufzfsuY3oqPT4ECzrE0wqAss=qthjvE1+CW2__FjuqAA@mail.gmail.com
Chaos Eternal <chaoseternal@shlug.org> skribis:
> existing implementations:
> Gambit-C: the termite module of gambit-c heavily depends on
> serializable closures to have functions like remote process call,
> process migration and remote spawn.
> chicken: chicken has termite port and also has these function implemented.
In Guile 2.0, you may be able to do implement closure serialization with
support from (system vm program).
(That will not be portable to 2.1/2.2, though.)
> I am porting termite to guile. that's why I am interesting in this.
Nice.
HTH,
Ludo’.
next prev parent reply other threads:[~2013-08-17 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 13:47 discussion: serialize procedures and continuations Chaos Eternal
2013-08-17 12:55 ` Ludovic Courtès [this message]
2014-03-23 20:25 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87li40xyrb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).