From: Andy Wingo <wingo@pobox.com>
To: guile-user <guile-user@gnu.org>
Subject: with-throw-handler -- how did I go this far without it
Date: Thu, 06 Nov 2008 12:09:45 +0100 [thread overview]
Message-ID: <m3vdv1dsau.fsf@pobox.com> (raw)
While reviewing the Guile manual this morning, trying to figure out how
to shoehorn the VM into it, I ran across the section on
`with-throw-handler', which is like `catch' but does modify the dynamic
context from which the throw occured.
In short: arrrrgh! I've wanted this for years and I didn't know it
existed! I've had to put up with crap backtraces for a long time, just
because some intermediate code did a catch and rethrow, losing the
initial context and thus the backtrace -- argh.
Hopefully everyone already knew about this, but I write in case someone
did not.
Happy hacking,
Andy
--
http://wingolog.org/
next reply other threads:[~2008-11-06 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 11:09 Andy Wingo [this message]
2008-11-07 23:13 ` with-throw-handler -- how did I go this far without it Neil Jerram
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=m3vdv1dsau.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@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).