unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Andy Wingo" <wingo@pobox.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: with-throw-handler -- how did I go this far without it
Date: Sat, 8 Nov 2008 00:13:09 +0100	[thread overview]
Message-ID: <49dd78620811071513w14fe1869pc2f867f00dcea211@mail.gmail.com> (raw)
In-Reply-To: <m3vdv1dsau.fsf@pobox.com>

On 06/11/2008, Andy Wingo <wingo@pobox.com> wrote:
>
>  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.

It's good to know that it's useful, but I don't completely understand.
 lazy-catch also preserves the backtrace, and that's been there for
ages.

   Neil




      reply	other threads:[~2008-11-07 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 11:09 with-throw-handler -- how did I go this far without it Andy Wingo
2008-11-07 23:13 ` Neil Jerram [this message]

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=49dd78620811071513w14fe1869pc2f867f00dcea211@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=guile-user@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).