From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: R6RS exception printing at the REPL
Date: Thu, 02 Dec 2010 00:16:40 +0100 [thread overview]
Message-ID: <87tyixulrb.fsf@gnu.org> (raw)
In-Reply-To: 871v63vhru.fsf@delenn.lan
Andreas Rottmann <a.rottmann@gmx.at> writes:
> Fitting that you mention this issue, since I have a question that I
> think also touches this area: what to do with exceptions not caught by
> the REPL (i.e. those leading to program termination when running a
> script)? My previous patch did not touch them, but I think they should
> be changed as well, as a crash with "guile: uncaught throw to
> r6rs:exception: (#<r6rs:record:&raise-object-wrapper>)" is clearly
> suboptimal.
While I just said I’m skeptical about global exception printers, I agree
that exception printing as in this example should be improved. So, hmm,
perhaps global exception printers are unavoidable?
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-12-01 23:16 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
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 [this message]
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=87tyixulrb.fsf@gnu.org \
--to=ludo@gnu.org \
--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).