From: rixed@happyleptic.org
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Why 3 different evaluators?
Date: Thu, 17 Nov 2011 06:29:21 +0100 [thread overview]
Message-ID: <20111117052919.GA1487@happyleptic.org> (raw)
In-Reply-To: <1321472632.6080.YahooMailNeo@web37902.mail.mud.yahoo.com>
-[ Wed, Nov 16, 2011 at 11:43:52AM -0800, Mike Gran ]----
> I believe that you can still run the whole test suite on the C evaluator
> by erasing all the .go files from the modules lib, setting auto compile off,
> then running the check-guile script.
I though it would run the evaluator written in scheme in that case.
next prev parent reply other threads:[~2011-11-17 5:29 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
2011-11-16 19:05 ` rixed
2011-11-16 19:43 ` Mike Gran
2011-11-17 5:29 ` rixed [this message]
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=20111117052919.GA1487@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).