From: Andy Wingo <wingo@pobox.com>
To: rixed@happyleptic.org
Cc: guile-user@gnu.org
Subject: Re: Why 3 different evaluators?
Date: Wed, 16 Nov 2011 19:48:58 +0100 [thread overview]
Message-ID: <87d3crlx7p.fsf@pobox.com> (raw)
In-Reply-To: <20111116101708.GA18426@ccellier.rd.securactive.lan> (rixed@happyleptic.org's message of "Wed, 16 Nov 2011 11:17:08 +0100")
On Wed 16 Nov 2011 11:17, rixed@happyleptic.org writes:
>> If I bootstrap Guile-X from GCC, I have to trust GCC.
>
> And the code for this C evaluator that's almost used nowhere thus
> probably much less tested than the rest of Guile.
On the contrary, it is used to interpret the entire compiler, when
compiling eval.go. It runs on every system that builds Guile. Also it
is very simple, and uses the same algorithm as eval.scm.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-11-16 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 5:00 Why 3 different evaluators? rixed
2011-11-16 9:31 ` Andy Wingo
2011-11-16 10:17 ` rixed
2011-11-16 18:48 ` Andy Wingo [this message]
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=87d3crlx7p.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=rixed@happyleptic.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).