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 -- take #2
Date: Fri, 11 Feb 2011 16:08:17 +0100 [thread overview]
Message-ID: <m3bp2iehi6.fsf@unquote.localdomain> (raw)
In-Reply-To: <87mxm9xcf5.fsf@gmx.at> (Andreas Rottmann's message of "Sun, 06 Feb 2011 19:09:34 +0100")
Hi Andreas,
On Sun 06 Feb 2011 19:09, Andreas Rottmann <a.rottmann@gmx.at> writes:
> exception-printer := port key args thunk -> nothing
I ended up adopting this. Thanks for the patch.
I reworked your patch a bit -- for example, print-exception is now in
boot-9, and used by C also. The C bits were actually more important to
me than the R6RS exceptions, so I poked that first.
> However, I think it would be more consistent to always print source
> information if available
> If we decide to do the source-information printing inside
> `print-exception' (as proposed above), we might think about deprecating
> `display-error' in favor of `print-exception'.
Done. I don't like display-error, let's stop using it. I didn't
actually deprecate display-error, but it's on the list... I guess
we need to fix the docs now.
> `display-error' cannot be implemented in terms of `print-exception', as
> the former is missing the `key' argument that the latter requires.
I just made it fabricate a "misc-error" key. It's not lying if no one
knows, right?
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-11 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 0:19 R6RS exception printing -- take #2 Andreas Rottmann
2011-02-01 1:07 ` Andreas Rottmann
2011-02-01 20:06 ` Andy Wingo
2011-02-06 18:09 ` Andreas Rottmann
2011-02-11 15:08 ` Andy Wingo [this message]
2011-02-07 12:07 ` [PATCH] " Andreas Rottmann
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=m3bp2iehi6.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).