From: Andy Wingo <wingo@pobox.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: despair, debugging, and the repl
Date: Thu, 10 Jun 2010 16:36:57 +0200 [thread overview]
Message-ID: <m3fx0vned2.fsf@pobox.com> (raw)
In-Reply-To: <87ljanxdi9.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Thu, 10 Jun 2010 14:45:18 +0200")
On Thu 10 Jun 2010 14:45, Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> () Andy Wingo <wingo@pobox.com>
> () Thu, 10 Jun 2010 12:03:22 +0200
>
> 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.
>
> If the plan is to modularize, is it possible to keep the old one around
> (in a module)?
The old repl, yes. I was wondering how to deprecate it in boot-9 but I
think I have figured out a way.
> Surely, not trashing Neil's work entirely is better?
Trashing is a loaded word :) It is always available in its original form
in git. But it hasn't worked, is the problem -- it relies on hooks from
ceval and deval that just aren't there any more. The part that coincides
with the new implementation is equivalent in functionality, though
Neil's code is nicer, I admit.
Guile needs to promote one main repl implementation, and one main
debugger. There is room for others, but if they are to remain in Guile
itself, they need to be maintained.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-06-10 14:36 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 [this message]
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
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=m3fx0vned2.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ttn@gnuvola.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).