From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: SRFI-1 in Scheme
Date: Tue, 20 Jul 2010 22:11:27 +0200 [thread overview]
Message-ID: <m34oftvrps.fsf@unquote.localdomain> (raw)
In-Reply-To: <87k4oqru11.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 20 Jul 2010 18:35:06 +0200")
Yo,
On Tue 20 Jul 2010 18:35, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> I would prefer not to enshrine a "regular / debug" split again though. I
>> guess that's what really bothers me. It's especially egregious if you
>> can't switch at runtime.
>
> The split survived! :-)
>
> $ guile -c 'sdf'
> ERROR: In procedure catch-closure:
> ERROR: Unbound variable: sdf
>
> $ guile --debug -c 'sdf'
> Backtrace:
[...]
Hehe. That, to me, is a bug ;-) What do you think about always giving
backtraces for uncaught errors? This does not impact regular vs debug
VMs, as thankfully we can walk any stack now.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-07-20 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 22:57 SRFI-1 in Scheme Ludovic Courtès
2010-07-13 21:25 ` Andy Wingo
2010-07-13 22:09 ` Ludovic Courtès
2010-07-13 22:27 ` Andy Wingo
2010-07-13 22:44 ` Ludovic Courtès
2010-07-14 7:41 ` Andy Wingo
2010-07-15 21:40 ` Ludovic Courtès
2010-07-19 20:30 ` Andy Wingo
2010-07-20 16:35 ` Ludovic Courtès
2010-07-20 20:11 ` Andy Wingo [this message]
2010-07-21 23:10 ` Ludovic Courtès
2010-07-20 20:15 ` Andy Wingo
2010-09-01 16:04 ` Allowing the choice of a VM engine? Ludovic Courtès
2010-09-03 5:23 ` Andy Wingo
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=m34oftvrps.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).