From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: despair, debugging, and the repl
Date: Thu, 10 Jun 2010 22:32:32 +0200 [thread overview]
Message-ID: <87631qpr1b.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3fx0vned2.fsf@pobox.com> (Andy Wingo's message of "Thu, 10 Jun 2010 16:36:57 +0200")
() Andy Wingo <wingo@pobox.com>
() Thu, 10 Jun 2010 16:36:57 +0200
The old repl, yes. I was wondering how to deprecate it in
boot-9 but I think I have figured out a way.
Cool.
> 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.
This suggests to me that the best course is to re-examine both
implementations in terms of high and low layers, substituting the
untenable low bits in Neil's code with the new low bits you wrote,
and keeping the high bits of Neil's code.
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.
Agreed. I think ultimately whoever does the work (sounds like
it's all you, in this case) decides, so i'll just briefly voice my
support for good documentation of the low bits, perhaps written
before doing anything else, so that if the above old-high/new-low
suggestion is not followed now, perhaps someone can follow it
later. (Everything is in Git, anyway, as you said.)
thi
next prev parent reply other threads:[~2010-06-10 20:32 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 [this message]
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=87631qpr1b.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-devel@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).