From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: SRFI-1 in Scheme
Date: Tue, 20 Jul 2010 18:35:06 +0200 [thread overview]
Message-ID: <87k4oqru11.fsf@gnu.org> (raw)
In-Reply-To: m3d3ujxlhq.fsf@unquote.localdomain
Hi,
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! :-)
--8<---------------cut here---------------start------------->8---
$ guile -c 'sdf'
ERROR: In procedure catch-closure:
ERROR: Unbound variable: sdf
$ guile --debug -c 'sdf'
Backtrace:
In ice-9/boot-9.scm:
170: 8 [catch #t #<catch-closure d5a660> ...]
In unknown file:
?: 7 [catch-closure]
In ice-9/boot-9.scm:
62: 6 [call-with-prompt prompt0 ...]
In module/ice-9/eval.scm:
389: 5 [eval # #]
In unknown file:
?: 4 [eval-string "sdf" #<undefined>]
In module/ice-9/eval.scm:
356: 3 [eval #<memoized sdf> ()]
In unknown file:
?: 2 [memoize-variable-access! #<memoized sdf> #<directory (guile-user) b60120>]
In ice-9/boot-9.scm:
115: 1 [#<procedure dd08c0 at ice-9/boot-9.scm:109:6 (thrown-k . args)> unbound-variable ...]
In unknown file:
?: 0 [catch-closure unbound-variable #f "Unbound variable: ~S" (sdf) #f]
ERROR: In procedure catch-closure:
ERROR: Unbound variable: sdf
$ guile --version
guile (GNU Guile) 1.9.11.176-1b912
--8<---------------cut here---------------end--------------->8---
Don’t get me wrong, this is not to say that we should make the split
even more acute!
I actually think that disabling automatic backtraces is much more
visible that disabling VM hooks.
What do you think?
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-07-20 16:35 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 [this message]
2010-07-20 20:11 ` Andy Wingo
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=87k4oqru11.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).