From: Mark H Weaver <mhw@netris.org>
To: "Göran Weinholt" <goran@weinholt.se>
Cc: 14922-done@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#14922: Improving R6RS exception handling in Guile
Date: Mon, 18 Nov 2013 01:16:58 -0500 [thread overview]
Message-ID: <87y54m5j51.fsf__18916.6750446477$1384755503$gmane$org@netris.org> (raw)
In-Reply-To: <87pptf8bz2.fsf@industria.weinholt.se> ("Göran Weinholt"'s message of "Thu, 15 Aug 2013 12:50:09 +0200")
Sorry for the long delay on this.
Göran Weinholt <goran@weinholt.se> writes:
> Mark H Weaver <mhw@netris.org> writes:
>
>> Hello all,
>>
>> I've cooked up a patch to help improve R6RS exception handling in Guile.
>>
>> As noted by Göran Weinholt in <http://bugs.gnu.org/14922>, the R6RS
>> exception handlers in Guile are currently unable to catch native Guile
>> exceptions. To fix this, the basic approach of this patch is to convert
>> native Guile exceptions into R6RS conditions within the R6RS exception
>> handlers.
> [...]
>> I'd be grateful for any feedback.
>
> I think it's the right approach to take. I've tested the patch a little
> and it's an improvement over the current state of affairs.
I went ahead and pushed this patch to stable-2.0. We can work on
incrementally improving it from there.
I'm closing this bug <http://bugs.gnu.org/14922>.
Thanks!
Mark
next prev parent reply other threads:[~2013-11-18 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87txixqxsp.fsf@tines.lan>
2013-08-15 10:50 ` bug#14922: Improving R6RS exception handling in Guile Göran Weinholt
[not found] ` <87pptf8bz2.fsf@industria.weinholt.se>
2013-11-18 6:16 ` Mark H Weaver [this message]
2013-07-21 9:29 bug#14922: guard expression doesn't catch everything Göran Weinholt
2013-08-10 17:07 ` bug#14922: Improving R6RS exception handling in Guile Mark H Weaver
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='87y54m5j51.fsf__18916.6750446477$1384755503$gmane$org@netris.org' \
--to=mhw@netris.org \
--cc=14922-done@debbugs.gnu.org \
--cc=goran@weinholt.se \
--cc=guile-devel@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).