From: Taylan Kammer <taylan.kammer@gmail.com>
To: J?r?my Korwin-Zmijowski <jeremy@korwin-zmijowski.fr>,
divoplade <d@divoplade.fr>,
srfi-64@srfi.schemers.org,
Mailing list Guile User <guile-user@gnu.org>
Subject: Re: test-equal: actual returned value is #f when tested expression raises execption
Date: Sun, 21 Feb 2021 15:21:59 +0100 [thread overview]
Message-ID: <5ee4017a-ccef-ffc0-4f32-a5d9ad3625ac@gmail.com> (raw)
In-Reply-To: <8ADFF799-7486-4DD4-BB68-82A216FF7ABC@korwin-zmijowski.fr>
On 20.02.2021 13:09, Jérémy Korwin-Zmijowski wrote:
> My concern here is that I did not defined the procedure in the module.
> It's empty.
I can reproduce this on Guile 2.2 (don't have access to 3.0 right now)
and in my opinion it's a bug.
I've also checked what my own SRFI-64 implementation does in this case,
and it reports the test as failed.
In my not-so-humble opinion, the reference implementation of SRFI-64,
which is what Guile ships with, is really terrible. The code is
unreadable and unsurprisingly you end up having bugs. It also doesn't
fully conform to its own specification.
My implementation is written as an R7RS module, which should work out of
the box with Guile 3.0 I suppose, since it supports R7RS. With earlier
versions of Guile, you can make it work like this:
(import (srfi srfi-1)
(srfi srfi-9)
(srfi srfi-11)
(srfi srfi-35)
(rnrs exceptions (6)))
(load "path/to/scheme-srfis/srfi/64/test-runner.body.scm")
(load "path/to/scheme-srfis/srfi/64/test-runner-simple.body.scm")
(load "path/to/scheme-srfis/srfi/64/source-info.body.scm")
(load "path/to/scheme-srfis/srfi/64/execution.body.scm")
The last line will produce a warning about possibly wrong number of
arguments to 'eval', but you can safely ignore that.
After this, use the regular SRFI-64 forms from the specification.
Here's the scheme-srfis repo that contains the implementation:
https://github.com/TaylanUB/scheme-srfis
In the README you can see a couple notes about the SRFI-64 of this
project. It offers two extensions that aren't in the standard.
- Taylan
prev parent reply other threads:[~2021-02-21 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 11:03 test-equal: actual returned value is #f when tested expression raises execption Jérémy Korwin-Zmijowski
2021-02-20 11:26 ` divoplade
2021-02-20 12:09 ` Jérémy Korwin-Zmijowski
2021-02-21 14:21 ` Taylan Kammer [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=5ee4017a-ccef-ffc0-4f32-a5d9ad3625ac@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=d@divoplade.fr \
--cc=guile-user@gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
--cc=srfi-64@srfi.schemers.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).