[Commit] New file

[Eli Zaretskii]

> Date: Wed, 26 May 2004 12:45:29 -0400
> From: Andrew Cagney <cagney@gnu.org>
> 
> > 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.

Yes.

My take of this is that IMHO the code in gdb-mi.el will bit-rot on the
Emacs side much faster than on the GDB side.  That is because the
GDB/MI API is supposed to change/evolve much slower than the Emacs
features related to gdb-mi.el.

It's true that GDB release cycle is much frequent than the Emacs
release cycle, but OTOH the pace of code changes checked into the
Emacs CVS is much faster than that of GDB.  Specifically, many
display-related features for which gdb-mi is an ideal application were
introduced during the the last couple of months alone.  There's no
comparable change in the MI interface and/or features.

> With GDB's more frequent release cycles there's a greater oportunity
> to expose the code to a wider audience.

As the Emacs CVS is accessible by anonymous, it's very easy to get the
latest gdb-mi.el.  So this is a non-issue, I think.