From: Jean Abou Samra <jean@abou-samra.fr>
To: guile-devel@gnu.org
Subject: (ice-9 sandbox) vs. (ice-9 safe)
Date: Sun, 24 Apr 2022 16:28:04 +0200 [thread overview]
Message-ID: <2e8891b4-5ae2-c137-9e52-7c3815c9e3de@abou-samra.fr> (raw)
Hi,
Guile 2.2 has a (ice-9 sandbox) module, documented at
https://www.gnu.org/software/guile/docs/docs-2.2/guile-ref/Sandboxed-Evaluation.html#index-make_002dsandbox_002dmodule
Earlier Guile already had the (ice-9 safe) module, which
provided a somewhat similar facility (which is also richer,
as it allows imposing time and memory limits on execution).
LilyPond currently uses (ice-9 safe) to implement its -dsafe mode.
Is it deprecated? Should we move to (ice-9 sandbox)? Is there anything
particular to be aware of in that transition that explains why (ice-9 safe)
remains around?
Thanks,
Jean
reply other threads:[~2022-04-24 14:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2e8891b4-5ae2-c137-9e52-7c3815c9e3de@abou-samra.fr \
--to=jean@abou-samra.fr \
--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).