GNU bug report logs - #39210
Guile 3.0: &assertion undefined in (rnrs conditions (6))

Previous Next

Package: guile;

Reported by: Ricardo Wurmus <rekado <at> elephly.net>

Date: Mon, 20 Jan 2020 22:33:02 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#39210: closed (Guile 3.0: &assertion undefined in (rnrs
 conditions (6)))
Date: Tue, 21 Jan 2020 16:59:01 +0000

[Message part 1 (text/plain, inline)]
Your message dated Tue, 21 Jan 2020 17:58:20 +0100
with message-id <87y2u0bvbn.fsf <at> gnu.org>
and subject line Re: bug#39210: Guile 3.0: &assertion undefined in (rnrs conditions (6))
has caused the debbugs.gnu.org bug report #39210,
regarding Guile 3.0: &assertion undefined in (rnrs conditions (6))
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
39210: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39210
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]
From: Ricardo Wurmus <rekado <at> elephly.net>
To: bug-guile <at> gnu.org
Subject: Guile 3.0: &assertion undefined in (rnrs conditions (6))
Date: Mon, 20 Jan 2020 23:31:48 +0100

The module (rnrs conditions (6)) exports &assertion but renames the
imported &assertion-failure to &assertion-violation (not &assertion).
Programs using &assertion from (rnrs conditions) fail with an unbound
variable error.

Using &violation instead of &assertion works.

--
Ricardo




[Message part 3 (message/rfc822, inline)]
From: Ludovic Courtès <ludo <at> gnu.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 39210-done <at> debbugs.gnu.org
Subject: Re: bug#39210: Guile 3.0: &assertion undefined in (rnrs conditions
 (6))
Date: Tue, 21 Jan 2020 17:58:20 +0100

Hello,

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> The module (rnrs conditions (6)) exports &assertion but renames the
> imported &assertion-failure to &assertion-violation (not &assertion).
> Programs using &assertion from (rnrs conditions) fail with an unbound
> variable error.
>
> Using &violation instead of &assertion works.

I believe commit 1b8e9ca0e37fab366435436995248abdfc780a10 fixes it.

Thanks!

Ludo’.
This bug report was last modified 5 years and 158 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.