unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Rottmann <a.rottmann@gmx.at>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: R6RS exception printing at the REPL
Date: Sat, 20 Nov 2010 19:18:20 +0100	[thread overview]
Message-ID: <87tyjbkger.fsf@delenn.lan> (raw)
In-Reply-To: <m3hbfc10jj.fsf@unquote.localdomain> (Andy Wingo's message of "Sat, 20 Nov 2010 16:23:44 +0100")

Andy Wingo <wingo@pobox.com> writes:

> On Sun 24 Oct 2010 23:46, Andreas Rottmann <a.rottmann@gmx.at> writes:
>
>> Attached is a patch that improves the way R6RS exceptions are printed at
>> the REPL
>
> Cool! I have also found the need to define pretty-printers for various
> throw keys. I wonder, could you rework this patch to add a more generic
> exception-printing mechanism?
>
Sure, that would make sense, and I can then also squash all the
occurances where exceptions are printed that I've missed in the last
patch.

> I'm going to display my ignorance in public and try to write down some
> types. := is a type definition, and : declares the type of something.
>
>   exception-printer := port args -> nothing
>
>   set-exception-printer! : exception-printer -> nothing
>
Did you mean the following?

set-exception-printer! : key exception-printer -> nothing

>   exception-printer : key -> exception-printer
>
>   print-exception : key args port -> nothing
>
> The default behavior could be hard-coded into print-exception. The first
> two procedures (set-exception-printer!, exception-printer, and
> print-exception) could go into boot-9, and the third into (system repl
> error-handling), or a new module under ice-9.
>
Sorry, I don't understand this -- there are three procedures, which you
all say should go into boot-9.scm?  Or did you mean that
`print-exception' should go into `(system repl error-handling)'?

> 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.

Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>



  reply	other threads:[~2010-11-20 18:18 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 [this message]
2010-11-20 20:19     ` Andy Wingo
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=87tyjbkger.fsf@delenn.lan \
    --to=a.rottmann@gmx.at \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).