unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: SRFI-1 in Scheme
Date: Thu, 15 Jul 2010 23:40:35 +0200	[thread overview]
Message-ID: <87iq4gfmp8.fsf@gnu.org> (raw)
In-Reply-To: m3mxtu8q86.fsf@unquote.localdomain

Hi!

Andy Wingo <wingo@pobox.com> writes:

> On Wed 14 Jul 2010 00:44, ludo@gnu.org (Ludovic Courtès) writes:
>
>> To clarify, I’d enable the debug engine for interactive use, but not for
>> ‘-s’, ‘-c’, and when a script is passed as an argument (analogous to
>> what 1.8 does with the evaluators.)
>
> I agree in principle, but I think the switching VMs bit is not fully
> baked yet, and so we should not recommend multiple VMs in 2.0. I would
> prefer to keep the situation as it is now, for 2.0.

OK, a conservative choice may be wiser for 2.0.

Just to make sure I understand, though: do you mean switching VMs “on
the fly” (i.e., changing the VM currently executing the code), or
switching VMs statically, before booting?  The latter (which is what I
had in mind) seems easy to do–unless I overlook something, that is.  :-)

Thanks,
Ludo’.






  reply	other threads:[~2010-07-15 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 22:57 SRFI-1 in Scheme Ludovic Courtès
2010-07-13 21:25 ` Andy Wingo
2010-07-13 22:09   ` Ludovic Courtès
2010-07-13 22:27     ` Andy Wingo
2010-07-13 22:44       ` Ludovic Courtès
2010-07-14  7:41         ` Andy Wingo
2010-07-15 21:40           ` Ludovic Courtès [this message]
2010-07-19 20:30             ` Andy Wingo
2010-07-20 16:35               ` Ludovic Courtès
2010-07-20 20:11                 ` Andy Wingo
2010-07-21 23:10                   ` Ludovic Courtès
2010-07-20 20:15                 ` Andy Wingo
2010-09-01 16:04               ` Allowing the choice of a VM engine? Ludovic Courtès
2010-09-03  5:23                 ` 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=87iq4gfmp8.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).