unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Howard <christopher@librehacker.com>
To: Guile User <guile-user@gnu.org>
Subject: srfi-64 apathetic test-error
Date: Tue, 22 Oct 2019 20:37:47 -0800	[thread overview]
Message-ID: <1571805467.17453.2.camel@librehacker.com> (raw)

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?


-- 
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social feed: https://gnusocial.club/librehacker
xmpp: creationist@member.fsf.org
otr: E9685B53 01F038DD D29281C9 30FDA71E BD0095D4
gnupg: 23FD5CC5 (keys.gnupg.net)
radio: KL1TL
featured: https://answersingenesis.org/


             reply	other threads:[~2019-10-23  4:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  4:37 Christopher Howard [this message]
2019-10-24 16:18 ` srfi-64 apathetic test-error Taylan Kammer
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=1571805467.17453.2.camel@librehacker.com \
    --to=christopher@librehacker.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).