From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Kevin Buettner <kevinb@redhat.com>,
Eli Zaretskii <eliz@elta.co.il>,
drow@mvista.com, gdb@sources.redhat.com
Subject: Re: [commit] Deprecate remaining STREQ uses
Date: Sat, 13 Dec 2003 20:03:00 -0000 [thread overview]
Message-ID: <vt2vfokmqrw.fsf@zenia.home> (raw)
In-Reply-To: <3FDA64D0.7020306@gnu.org>
[switched to gdb@]
Andrew Cagney <cagney@gnu.org> writes:
> > I suspect that what this boils down to is a difference in maintenance
> > philosophy: I would prefer to see old (deprecated) interfaces eliminated
> > as soon as possible even if it does involve touching possible candidates
> > for deletion, whereas you don't seem to mind having old interfaces
> > retained for longer periods of time.
>
> To make this more concrete, perhaphs you could outline how this would
> have worked with the old vs new frame code.
Everyone posting so far has agreed that there are cases that are so
complex that deprecation is an appropriate strategy. Having tried to
incrementally update a port from the old to the new frame interfaces,
but instead having given up and just rewritten it from scratch, I
would say that many aspects of the frame interface are clearly on the
"deprecation is appropriate" side of the line.
The issue at hand, STREQ, and the issue Kevin raised, complaints, are
cases that should have been on the other side of that line: just get
rid of the old uses immediately. Maybe not in the same commit, but
certainly before taking up other projects.
But I think this principle does apply to the frame interfaces, just on
a different time scale:
After GDB 6.0 was released, you floated some ideas about renovating
the target vector. While I like the direction these were going, I was
a little distressed to think that we were going to begin the process
of introducing a whole new class of deprecated target-related
interfaces before we had even finished removing uses of the deprecated
frame interfaces. Certainly, we shouldn't wait for backwater *-tdep.c
files that nobody can test, but we still have deprecated frame
machinery in actively maintained targets like the MIPS and the
PowerPC.
I recognize that you and others have been working on these; I don't
mean to complain or be unappreciative. But I think we should get
those taken care of before plunging into deprecating interfaces from
an entirely new section of GDB.
next parent reply other threads:[~2003-12-13 20:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FC119EB.1060102@gnu.org>
[not found] ` <ufzgee29u.fsf@elta.co.il>
[not found] ` <3FC234C0.1000500@gnu.org>
[not found] ` <20031124165047.GA2227@nevyn.them.org>
[not found] ` <1031124182547.ZM9776@localhost.localdomain>
[not found] ` <3FC26407.9000704@gnu.org>
[not found] ` <1031125000932.ZM11256@localhost.localdomain>
[not found] ` <3FC60A75.8090803@gnu.org>
[not found] ` <1031204044404.ZM3660@localhost.localdomain>
[not found] ` <9743-Thu04Dec2003174358+0200-eliz@elta.co.il>
[not found] ` <3FCF6FCA.30607@gnu.org>
[not found] ` <1031212192642.ZM21819@localhost.localdomain>
[not found] ` <3FDA64D0.7020306@gnu.org>
2003-12-13 20:03 ` Jim Blandy [this message]
2003-12-14 16:24 ` Andrew Cagney
2003-12-31 19:56 Michael Elizabeth Chastain
2004-01-01 6:03 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-12-15 17:01 Michael Elizabeth Chastain
2003-12-15 6:22 Michael Elizabeth Chastain
2003-12-15 6:39 ` Eli Zaretskii
2003-12-15 15:51 ` Daniel Jacobowitz
2003-12-16 6:30 ` Eli Zaretskii
2003-12-31 19:48 ` Andrew Cagney
2004-01-01 5:59 ` Eli Zaretskii
2003-12-14 16:02 Michael Elizabeth Chastain
2003-12-14 18:13 ` Eli Zaretskii
2003-12-14 8:25 Michael Elizabeth Chastain
2003-12-14 11:45 ` Eli Zaretskii
2003-12-14 14:44 ` Andrew Cagney
[not found] <20031214062335.964804B412@berman.michael-chastain.com>
2003-12-14 6:34 ` Eli Zaretskii
2003-12-13 15:23 Michael Elizabeth Chastain
2003-12-13 16:31 ` Eli Zaretskii
2003-12-13 19:40 ` Andrew Cagney
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=vt2vfokmqrw.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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