Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nick Roberts <nickrob@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [Commit] New file
Date: Wed, 26 May 2004 16:45:00 -0000	[thread overview]
Message-ID: <40B4C9A9.3040904@gnu.org> (raw)
In-Reply-To: <6654-Wed26May2004124733+0300-eliz@gnu.org>

From: Nick Roberts <nickrob@gnu.org>
Date: Tue, 25 May 2004 21:07:39 +0100

New elisp file which provides a graphical user interface to GDB for Emacs.


IMHO, it shouldn't have been committed without discussion (either
RFA/RFC here or even a general discussion on gdb@sources.redhat.com)..
I've appologized for my foobar.

I personally don't like the idea of having an Emacs file in the GDB
distribution.  We had such a file in the past, and the result was that
it could never be in sync with the Emacs code base.  I'm unwilling to
go through that experience once again.
As this code evolves it is going to find that it is caught between two 
competing masters: GDB; and EMACS.  For each we'll need to juggle both 
interface and release cycle concerns.  As such we need to decide which 
of those two masters is, at least for the moment, more important.

- the current development focus is on GDB's MI
At present the goal is to get the code working with MI, and that, very 
likely will mean extending the MI interface.  A given iteration of this 
code will very likely be specific to >= vN of GDB.

- the current development is work-in-progress
At present this code is very much in its development phase.  With GDB's 
more frequent release cycles there's a greater oportunity to expose the 
code to a wider audience.

Long term, as this .el file and MI mature, returning the code to EMACS 
will likely make sense.  I think we're 1-2 GDB releases away from that 
though.

Andrew




  reply	other threads:[~2004-05-26 16:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 20:07 Nick Roberts
2004-05-25 22:36 ` Andrew Cagney
2004-05-26  9:54   ` Eli Zaretskii
2004-05-26  9:51 ` Eli Zaretskii
2004-05-26 16:45   ` Andrew Cagney [this message]
2004-05-27  7:23     ` Eli Zaretskii
2004-05-27 20:19       ` Andrew Cagney
2004-05-28  7:54         ` Eli Zaretskii
2004-05-28 19:52           ` Nick Roberts
2004-05-31 19:07             ` Andrew Cagney
2004-06-01  4:35               ` Eli Zaretskii
2004-06-01 20:09                 ` Nick Roberts
2004-06-01 22:21                   ` Eli Zaretskii
2004-05-26 20:43   ` Nick Roberts

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=40B4C9A9.3040904@gnu.org \
    --to=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@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