unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: despair, debugging, and the repl
Date: Mon, 14 Jun 2010 23:38:17 +0200	[thread overview]
Message-ID: <m31vc9l2gm.fsf@pobox.com> (raw)
In-Reply-To: <87d3vt4lxr.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 14 Jun 2010 18:29:36 +0200")

On Mon 14 Jun 2010 18:29, ludo@gnu.org (Ludovic Courtès) writes:

>> So, to that end, then, here's a preliminary plan of action:
>>
>>   * Deprecate all of the old repl code, keeping compatibility shims for
>>     the useful interfaces perhaps, but trying to move the REPL
>>     implementation entirely out to modules.
>>
>>   * Remove all of the old debugger code. This pains me somewhat, but we
>>     have to move forward here.
>>
>>   * Deprecate the-last-stack fluid -- besides being hard to reason
>>     about, it doesn't even work all that well.
>>
>>   * Document the new REPL.
>
> Fine with me (but maybe you’ve already finished it in the meantime).

No, there are still some repl bits of boot-9 that need limning. I
skipped over some parts when revising boot-9 recently, and hope to come
back to them soonish.

> What about single-stepping

Should be possible, given source line info and the next-instruction
hook.

> and expression-level debugging?

Trickier, we'll need expression-level debug info in the procedure. And
which expressions, the expanded ones or the ones from the original
source? I think I'd need to spend some times with other schemes to
figure this out.

Breakpoints would be good too.

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2010-06-14 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 10:03 despair, debugging, and the repl Andy Wingo
2010-06-10 12:45 ` Thien-Thi Nguyen
2010-06-10 14:36   ` Andy Wingo
2010-06-10 20:32     ` Thien-Thi Nguyen
2010-06-13 12:13 ` Neil Jerram
2010-06-14 16:29 ` Ludovic Courtès
2010-06-14 21:38   ` Andy Wingo [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=m31vc9l2gm.fsf@pobox.com \
    --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).