From: Taylan Kammer <taylan.kammer@gmail.com>
To: guile-user@gnu.org
Subject: Re: srfi-64 apathetic test-error
Date: Thu, 24 Oct 2019 18:18:52 +0200 [thread overview]
Message-ID: <5d7fb138-a870-826f-2a68-a539c90da813@gmail.com> (raw)
In-Reply-To: <1571805467.17453.2.camel@librehacker.com>
On 23.10.2019 06:37, Christopher Howard wrote:
> Hi, I was just wondering: `test-error' from (srfi srfi-64) gives a pass
> if it catches an exception, but it doesn't seem to care whether or not
> the exception caught matches what you told it to expect. Is this a bug?
The (test-error ...) form takes an optional "error-type" operand. It
can be an arbitrary predicate (one-argument procedure that returns a
Boolean value) which tests if the error is the expected kind.
See here for a complete documentation of the SRFI-64 API:
https://srfi.schemers.org/srfi-64/srfi-64.html
- Taylan
next prev parent reply other threads:[~2019-10-24 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 4:37 srfi-64 apathetic test-error Christopher Howard
2019-10-24 16:18 ` Taylan Kammer [this message]
2019-10-24 16:21 ` John Cowan
2019-10-24 16:50 ` Taylan Kammer
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=5d7fb138-a870-826f-2a68-a539c90da813@gmail.com \
--to=taylan.kammer@gmail.com \
--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).