From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neiljerram@googlemail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: debugger in 2.0?
Date: Sun, 14 Mar 2010 23:02:28 +0100 [thread overview]
Message-ID: <m3fx425zpn.fsf@pobox.com> (raw)
In-Reply-To: <m3mxya61vn.fsf@pobox.com> (Andy Wingo's message of "Sun, 14 Mar 2010 22:15:40 +0100")
On Sun 14 Mar 2010 22:15, Andy Wingo <wingo@pobox.com> writes:
> I wanted to write to say that I was considering combing (ice-9 debugger)
> for salvageable code
ISTR You mentioned once that you weren't comfortable with the OO traps
layer (or was that breakpoints?) -- actually could you clarify that? The
interfaces look good to me.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-03-14 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 21:15 debugger in 2.0? Andy Wingo
2010-03-14 22:02 ` Andy Wingo [this message]
2010-03-16 23:36 ` Neil Jerram
2010-03-16 21:48 ` 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=m3fx425zpn.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=neiljerram@googlemail.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).