This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [commit] Deprecate remaining STREQ uses
- From: Kevin Buettner <kevinb at redhat dot com>
- To: Andrew Cagney <cagney at gnu dot org>, Kevin Buettner <kevinb at redhat dot com>
- Cc: Daniel Jacobowitz <drow at mvista dot com>, gdb-patches at sources dot redhat dot com
- Date: Wed, 3 Dec 2003 21:44:04 -0700
- Subject: Re: [commit] Deprecate remaining STREQ uses
- References: <3FC119EB.1060102@gnu.org> <ufzgee29u.fsf@elta.co.il> <3FC234C0.1000500@gnu.org> <20031124165047.GA2227@nevyn.them.org> <1031124182547.ZM9776@localhost.localdomain> <3FC26407.9000704@gnu.org> <1031125000932.ZM11256@localhost.localdomain> <3FC60A75.8090803@gnu.org>
On Nov 27, 9:30am, Andrew Cagney wrote:
> > Even if the process isn't entirely automated, it's still sometimes
> > better to do the conversion all at once. By deprecating something,
> > you're forcing someone else (or even a later version of yourself) to
> > deal with the problem later on.
>
> If a contributor wants to add new code, or fix bugs in existing code,
> they should not be increasing the use of existing deprecated mechanisms
> (after all we should be able to reasonably expect contributors to not
> make matters worse). The prime motivator here should our joint goal to
> make GDB the best debgger possible, and more immediatly our desire to
> fix bugs such as those identified by my rewritten structs.exp. As for
> other code, let it bitrot and die.
I agree with much of what you say, but I really can't agree with the
last part. There is a quite a lot of code which simply cannot be
allowed to "bitrot and die".
I have already stated that I think the renaming of deprecated
interfaces is okay in some instances. I am concerned, however, that
this approach is being used in instances where it doesn't really
need to be.
Kevin