From: Andy Wingo <wingo@pobox.com>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: R6RS exception printing at the REPL
Date: Sat, 20 Nov 2010 21:19:18 +0100 [thread overview]
Message-ID: <m34obb21fd.fsf@unquote.localdomain> (raw)
In-Reply-To: <87tyjbkger.fsf@delenn.lan> (Andreas Rottmann's message of "Sat, 20 Nov 2010 19:18:20 +0100")
Heya Andreas,
On Sat 20 Nov 2010 19:18, Andreas Rottmann <a.rottmann@gmx.at> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> set-exception-printer! : exception-printer -> nothing
>>
> Did you mean the following?
>
> set-exception-printer! : key exception-printer -> nothing
Of course, yes. It seems I distilled the interface down past its
essentials! ;)
> Did you mean that `print-exception' should go into `(system repl
> error-handling)'?
This, that print-exception could go into (system repl
error-handling). The reason for this would be to allow the default
exception printer, embedded in print-exception, to use other modules,
like match or pmatch or the like. I think?
>> What do you think?
>>
> Besides the above questions, I wonder where I should install the
> exception printer for R6RS exceptions (since the code will depend on
> quite a bit of R6RS, so we maybe want to have it loaded on demand, like
> in the last patch.
Good question.
For r6rs exceptions, I think either (rnrs conditions) or (rnrs
exceptions).
For srfi-35 conditions, either we make another registry for printers of
srfi-34 [sic] exceptions, or just assume that people using srfi-34
probably want srfi-35 as well, and have srfi-35 define the printer for
srfi-34 exceptions.
Thanks for the patch, and for dealing with a fickle maintainer!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-11-20 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 21:46 R6RS exception printing at the REPL Andreas Rottmann
2010-11-20 15:23 ` Andy Wingo
2010-11-20 18:18 ` Andreas Rottmann
2010-11-20 20:19 ` Andy Wingo [this message]
2010-11-27 0:08 ` Andreas Rottmann
2010-11-29 20:15 ` @ and @@ in r6rs libs [Was: R6RS exception printing at the REPL] Andy Wingo
2010-11-29 22:35 ` Andreas Rottmann
2010-11-29 20:34 ` R6RS exception printing at the REPL Andy Wingo
2010-11-29 23:20 ` Andreas Rottmann
2010-12-01 23:16 ` Ludovic Courtès
2010-12-01 23:13 ` Ludovic Courtès
2010-12-02 20:21 ` Andreas Rottmann
2010-12-13 16:49 ` 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=m34obb21fd.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=a.rottmann@gmx.at \
--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).