From: "Ludovic Courtès" <ludo@gnu.org>
To: Klaus Stehle <klaus.stehle@uni-tuebingen.de>
Cc: 39509-done@debbugs.gnu.org
Subject: bug#39509: guile-3.0.0: Error while printing exception
Date: Fri, 06 Mar 2020 18:09:39 +0100 [thread overview]
Message-ID: <87o8t9l8a4.fsf@gnu.org> (raw)
In-Reply-To: <20200208094103.Horde.krHZmxII44Qu3ouivhN9Scu@webmail.uni-tuebingen.de> (Klaus Stehle's message of "Sat, 08 Feb 2020 09:41:03 +0100")
Hi Klaus,
Klaus Stehle <klaus.stehle@uni-tuebingen.de> skribis:
> ;; The compiled program II says: "Error while printing exception".
> ;; It doesn't matter which function produces the string for the error message.
> ;; The compiled version does not work, if the message string is the returned
> ;; value of a function. The pure example:
>
> (error ((lambda () "If compiled we won't see this error message!")))
This is now fixed in commit d49453259bf97aed6d7e41d1bb364b62310c088f,
which will be in 3.0.1.
Thanks!
Ludo’.
prev parent reply other threads:[~2020-03-06 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 8:41 bug#39509: guile-3.0.0: Error while printing exception Klaus Stehle
2020-03-06 17:09 ` Ludovic Courtès [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=87o8t9l8a4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39509-done@debbugs.gnu.org \
--cc=klaus.stehle@uni-tuebingen.de \
/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).