From: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-user@gnu.org
Subject: Re: to serialize/deserialize closures; and multithreading
Date: 25 Mar 2004 07:40:29 -0500 [thread overview]
Message-ID: <rmismfxyu9u.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0403250050390.22664-100000@localhost.localdomain>
1. If I have a scheme value that is a closure, is there any way that I can
serialize this closure (from C code) into a form that it can be
deserialized back into a SCM closure variable (again, by C code)? I can
assume for this question that both ends of the serial line are running the
same version of gnu guile and my software, but cannot assume that both
ends are running on the same computer architecture. Would it instead
only be possible for me to transfer closures as their scheme source.
I'm not even sure it is well-defined what it means to migrate a
closure. Should a mutation on the new computer of a captured variable
affect the old computer?
--
Greg Troxel <gdt@ir.bbn.com>
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-25 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 6:19 to serialize/deserialize closures; and multithreading Nicholas Paul Johnson
2004-03-25 6:43 ` Paul Jarc
2004-03-25 12:40 ` Greg Troxel [this message]
2004-03-25 17:18 ` Lynn Winebarger
2004-03-25 18:11 ` Lynn Winebarger
2004-03-25 19:55 ` Paul Jarc
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 22:38 Faraz Shahbazker
2004-03-26 13:05 ` rm
2004-03-26 15:22 ` Nicholas Paul Johnson
2004-03-26 20:02 Faraz Shahbazker
2004-03-26 20:35 ` Andreas Rottmann
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=rmismfxyu9u.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-user@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).