From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Exception API
Date: Tue, 05 Sep 2006 08:58:58 +1000 [thread overview]
Message-ID: <87wt8jkzm5.fsf@zip.com.au> (raw)
In-Reply-To: <87mz9gt3ia.fsf@laas.fr> (Ludovic Courtès's message of "Mon, 04 Sep 2006 10:55:25 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> (let ((errno (car (cadddr args)))) ;; !!!
system-error-errno helps there. I made a few similar extracting funcs
at one time ... then found it better not to try to be too smart about
analysing errors!
> (guard (c ((i/o-no-such-file-error? c)
I had trouble understanding the different dynamic environments
specified for that srfi-34 guard. It looked worryingly like there
could be jumps out of the originating continuation and then back in if
there's a re-throw, which could be pretty slow with guile's
continuations.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-09-04 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 20:10 saving and restoring the error stack trace Marco Maggi
2006-09-04 8:55 ` Exception API Ludovic Courtès
2006-09-04 22:58 ` Kevin Ryde [this message]
2006-09-07 22:23 ` Neil Jerram
2006-09-12 9:36 ` Ludovic Courtès
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=87wt8jkzm5.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).