unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: rixed@happyleptic.org
To: guile-user@gnu.org
Subject: Why 3 different evaluators?
Date: Wed, 16 Nov 2011 06:00:05 +0100	[thread overview]
Message-ID: <20111116050005.GA19554@happyleptic.org> (raw)

According to the doc, guile currently maintain 3 evaluators:

- the new VM
- an evaluator written in scheme
- the old C evaluator, used for bootstrapping the compiler.

That's a lot of code just to bootstrap the compiler.  Why not bootstrapping the
compiler from either previous installed guile or (as fall-back) some provided
.go bytecode instead? Wouldn't that make guile code significantly simpler to
maintain and faster to compile?




             reply	other threads:[~2011-11-16  5:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16  5:00 rixed [this message]
2011-11-16  9:31 ` Why 3 different evaluators? Andy Wingo
2011-11-16 10:17   ` rixed
2011-11-16 18:48     ` Andy Wingo
2011-11-16 19:05       ` rixed
2011-11-16 19:43       ` Mike Gran
2011-11-17  5:29         ` rixed
2012-01-09 22:16           ` 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=20111116050005.GA19554@happyleptic.org \
    --to=rixed@happyleptic.org \
    --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).