From: Sunjoong Lee <sunjoong@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org, Per Bothner <per@bothner.com>
Subject: Re: SRFI-64 implementation for Guile 2.0
Date: Sat, 21 Apr 2012 02:36:49 +0900 [thread overview]
Message-ID: <CAK93xhoiEv6rAatrknwQ=YW8xPp4eUFR10cnssep79Rf_70Lmg@mail.gmail.com> (raw)
In-Reply-To: <87d372mnyl.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
Hi, Ludo’;
Your implementation fails srfi-64-test.scm, a test suite for the SRFI 64.
Per:
I realize the test-error of the reference implementation has a bug;
It calls %test-error like this - (test-assert (%test-error etype expr))
but %test-error needs three arguments - (%test-error r etype expr) !!
I think you may fix it.
Humm... in %test-error (and srfi-34 srfi-35) case, (equal? type #t) is a
typo of (equal? etype #t), I think.
Ludo’:
"Store the test log in UTF-8" is a good idea.
I don't know "Display a backtrace upon error."
In my implementation on Guile and Per's reference implementation on
Kawa, actual-error is loged if exception occurs like this;
Test begin:
test-name: "3.3. test-begin with mismatched test-end"
source-file: "srfi-64-test.scm"
source-line: 236
source-form: (test-error "3.3. test-begin with mismatched test-end" #t
(triv-runner (lambda () (test-begin "a") (test-assert "b" #t) (test-end
"x"))))
Test end:
result-kind: pass
actual-error: (misc-error #f "~A" ("bad end grojup name a but expected
x") #f)
expected-error: #t
2012/4/21 Ludovic Courtès <ludo@gnu.org>
>
> Per Bothner <per@bothner.com> skribis:
>
> > I think it would be great to get SRFI-64 into Guile.
>
> Me too.
>
> FWIW, I’ve been using an almost-unmodified version in several projects:
>
> http://git.savannah.gnu.org/cgit/libchop.git/tree/guile2/srfi
>
[-- Attachment #2: Type: text/html, Size: 2233 bytes --]
next prev parent reply other threads:[~2012-04-20 17:36 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
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 [this message]
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='CAK93xhoiEv6rAatrknwQ=YW8xPp4eUFR10cnssep79Rf_70Lmg@mail.gmail.com' \
--to=sunjoong@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).