From: Sunjoong Lee <sunjoong@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: guile-user@gnu.org
Subject: Re: SRFI-64 implementation for Guile 2.0
Date: Sat, 14 Apr 2012 21:43:24 +0900 [thread overview]
Message-ID: <CAK93xhpCz-tRYm4oypjKrCme4UbkFeJ8XVx4pL0p5K65NiBF2w@mail.gmail.com> (raw)
In-Reply-To: <4F88DB8D.9050203@bothner.com>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
I rewrote srfi/srfi-64.scm file using cond-expand but don't know it works.
On Guile 2.0, it works;
$ guile -L `pwd` --use-srfi=64 srfi-64-test.scm
%%%% Starting test SRFI 64 - Meta-Test Suite (Writing full log to "SRFI
64 - Meta-Test Suite.log")
# of expected passes 51
# of expected failures 2
2012/4/14 Per Bothner <per@bothner.com>
> This is nice. It would be great if the Guile port would be merged
> into the reference implementation, presumably using cond-expand.
> That way bug-fixes or changes in one could be more easily be
> merged into the other.
>
I have no idea how to use your testing.scm file on Kawa or Chicken.
Without testing.scm file, srfi-64-test.scm can be checked on Kawa;
$ kawa srfi-64-test.scm
%%%% Starting test SRFI 64 - Meta-Test Suite (Writing full log to "SRFI
64 - Meta-Test Suite.log")
# of expected passes 51
# of expected failures 2
I don't know how to use testing.scm and my srfi/srfi-64.scm on Kawa.
[-- Attachment #1.2: Type: text/html, Size: 1441 bytes --]
[-- Attachment #2: srfi-64.scm.gz --]
[-- Type: application/x-gzip, Size: 7606 bytes --]
next prev parent reply other threads:[~2012-04-14 12:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 21:53 SRFI-64 implementation for Guile 2.0 Sunjoong Lee
2012-04-14 1:39 ` Sunjoong Lee
2012-04-14 2:06 ` Per Bothner
2012-04-14 12:43 ` Sunjoong Lee [this message]
2012-04-15 20:35 ` Sunjoong Lee
2012-04-20 2:50 ` Noah Lavine
2012-04-20 4:21 ` Per Bothner
2012-04-20 10:19 ` Sunjoong Lee
2012-04-20 18:27 ` Per Bothner
2012-04-20 20:53 ` Sunjoong Lee
2012-04-20 15:18 ` Ludovic Courtès
2012-04-20 17:36 ` Sunjoong Lee
2012-04-21 23:08 ` Ludovic Courtès
2012-04-23 6:07 ` Sunjoong Lee
2012-12-28 3:22 ` Per Bothner
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=CAK93xhpCz-tRYm4oypjKrCme4UbkFeJ8XVx4pL0p5K65NiBF2w@mail.gmail.com \
--to=sunjoong@gmail.com \
--cc=guile-user@gnu.org \
--cc=per@bothner.com \
/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).