unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Roadmap and goals?
Date: Thu, 18 Apr 2002 14:26:18 -0500	[thread overview]
Message-ID: <87elhcerl1.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0204181636520.19122-100000@phantom.h07.org> (bitwize@wizards-of-source.org's message of "Thu, 18 Apr 2002 16:58:25 +0200 (CEST)")

bitwize@wizards-of-source.org writes:

> It may be too much to ask, but I'd like to see a VM being integrated
> into guile-core. The one that Keisuke Nishida wrote a while back is
> supposedly really good; integrating it so that byte-compilation and
> execution of bytecodes becomes the default method of interpretation
> and execution (much as it is with mzscheme) would be a Good Thing
> for Guile, performance-wise.

A VM is possible, but see the other recent notes on what probably
needs to happen first, in particular Marius' (and my) recent mails
about the macro system, module system cleanups, etc.

> Responding to .NET, SOAP, and all that hype-based hoopla with
> efficient Scheme-based simple RPC and secure mobile code mechanisms
> would be nifty.

One thing you might want to check out is ice-9/safe.scm if you haven't
looked at it yet.  It's not what you're talking about above, but it
does allow you to create environments where it's supposed to be safe
to eval random-untrusted-code and have very careful control over what
it could possibly do.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-04-18 19:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 12:21 Roadmap and goals? Tanel Tammet
2002-04-17 20:59 ` Neil Jerram
2002-04-18  8:37   ` Panagiotis Vossos
2002-04-19  9:14     ` Panagiotis Vossos
2002-04-20  6:58       ` Thien-Thi Nguyen
2002-04-20 10:18         ` Panagiotis Vossos
2002-04-18 14:58   ` bitwize
2002-04-18 19:26     ` Rob Browning [this message]
2002-04-20  7:23   ` Thien-Thi Nguyen
2002-04-18  0:57 ` Christopher Cramer
2002-04-19 17:36   ` Marius Vollmer
2002-04-19  8:38 ` Nicolas Neuss
2002-04-21 15:14   ` Rob Browning
2002-04-21 22:26   ` bitwize
2002-04-22 18:36     ` Kirill Lisovsky
2002-04-23  7:53       ` rm
2002-04-23 15:11         ` Rob Browning
2002-04-20  7:47 ` Thien-Thi Nguyen
2002-05-14  8:26   ` Thien-Thi Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20 12:55 Kirill Lisovsky
2002-04-20 20:01 ` Rob Browning

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=87elhcerl1.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.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).