From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Matthew Keeter <matt.j.keeter@gmail.com>
Cc: guile-user@gnu.org, Roberto Baleno <roberto.baleno@gmail.com>
Subject: Re: Embedding Guile with sandboxing
Date: Wed, 25 Nov 2015 08:36:22 -0600 [thread overview]
Message-ID: <87fuzujgbe.fsf@dustycloud.org> (raw)
In-Reply-To: <C15AB3DE-EA3D-42F6-921F-933C49259A15@gmail.com>
Antimony looks really cool!
I agree that Guile doesn't provide a silver bullet here. Again, I think
it can be done... though I think it'll require a lot of yak hair
traversal to get to that point :)
Good luck, have fun, and happy hacking!
prev parent reply other threads:[~2015-11-25 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 18:35 Embedding Guile with sandboxing Matthew Keeter
2015-11-21 21:39 ` Pascal J. Bourguignon
2015-11-24 16:35 ` Amirouche Boubekki
2015-11-21 21:40 ` Thompson, David
2015-11-22 10:06 ` Arne Babenhauserheide
2015-11-25 11:07 ` tomas
2015-11-22 15:51 ` Christopher Allan Webber
2015-11-23 0:50 ` Roberto Baleno
2015-11-23 14:55 ` Matthew Keeter
2015-11-25 14:36 ` Christopher Allan Webber [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
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=87fuzujgbe.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=matt.j.keeter@gmail.com \
--cc=roberto.baleno@gmail.com \
/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).