Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Allow printing of Guile values
Date: Fri, 20 Jul 2007 19:37:00 -0000	[thread overview]
Message-ID: <871wf3x7er.fsf@chbouib.org> (raw)
In-Reply-To: <m3bqe76kot.fsf@codesourcery.com>

Hi Jim,

Jim Blandy <jimb@codesourcery.com> writes:

> Definitely.  Part of the rationale for deleting it was, "Oh, if
> someone shows up to keep it alive, we've still got it in CVS."  I'll
> be happy to review changes.  The key is that someone make themselves
> available to keep it working.

Great.

> A debugger should be able to inspect the state of programs in serious
> disarray, so there's an argument against relying too much on invoking
> functions in Guile.  Certainly, though, the best code would draw a
> clear distinction between scm-lang.c and scm-lang-guile.c.

Agreed.  However, to be very pragmatic, we may be better off with
minimal support that works and doesn't add a significant maintenance
burden.  For instance, while valuable, interpretation of Guile values on
the GDB side requires a significant amount of code that must be kept in
sync with Guile.

How would you like to proceed: would you like to reinstall the deleted
files and patch against them, or would you prefer that we somehow start
anew?

Thanks,
Ludovic.


  reply	other threads:[~2007-07-20 18:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 15:19 Ludovic Courtès
2007-07-20 15:57 ` Daniel Jacobowitz
2007-07-20 16:49   ` Ludovic Courtès
2007-07-20 18:22     ` Jim Blandy
2007-07-20 19:37       ` Ludovic Courtès [this message]
2007-07-20 20:12         ` Jim Blandy
2007-07-20 21:18           ` Ludovic Courtès
2007-07-28  1:17 ` Jim Blandy
2007-07-28 16:48   ` Ludovic Courtès
2007-08-07 18:50     ` Jim Blandy
2007-08-09 21:54       ` Ludovic Courtès
2007-08-09 22:30         ` Eli Zaretskii
2007-08-09 23:03       ` Ludovic Courtès
2007-08-03 21:38 ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871wf3x7er.fsf@chbouib.org \
    --to=ludo@gnu.org \
    --cc=gdb-patches@sources.redhat.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