From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: r5rs pitfall test
Date: 03 May 2003 22:01:35 +0200 [thread overview]
Message-ID: <87issrdckg.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20030213150507.394a936c.dsmith@altustech.com>
[You'd never think you get an answer this late, right? ;-]
"Dale P. Smith" <dsmith@altustech.com> writes:
> I saw this on comp.lang.scheme and thought I'd try it out:
>
> http://sisc.sourceforge.net/r5rspitresults.html
Thanks! I added these tests to the HEAD test suite.
> Guile fails tests 1.1 and 2.1
I didn't fix these bugs right away since I didn't understand 1.1 right
away and 2.1 is relatively hard to fix, given the internal structure
of our evaluator. I'd say 2.1 (at least) isn't very important to fix,
tho.
If anyone feels motivated... :-)
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-05-03 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 20:05 r5rs pitfall test Dale P. Smith
2003-05-03 20:01 ` Marius Vollmer [this message]
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=87issrdckg.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--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).