From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: Why do functions objfpy_new and pspy_new exist?
Date: Thu, 02 Oct 2014 22:11:00 -0000 [thread overview]
Message-ID: <542DCD9B.9010400@earthlink.net> (raw)
In-Reply-To: <CADPb22TKh6s-NN61HHu=mwf99uu6hTQHOH+GEiVeZmg++H58Zw@mail.gmail.com>
On 9/25/14, 3:07 PM, Doug Evans wrote:
[...]
>
> I know I've mentioned this before, but since the topic has come up again,
> I think GDB could have a formal deprecation process that would allow
> us to remove things we'd like to remove (this is for API-like things
> which are harder to remove than, e.g., outdated ports).
Nominally, the existing process is as described at
https://sourceware.org/gdb/wiki/Internals%20Obsoleting-code
We've also done "deprecate in one release, remove in the next", and
added "deprecated_" onto function names and such. Empirically, it
hasn't created the desired urgency - people have been content to keep
calling deprecated_foo for many years after its deprecation. :-)
Stan
stan@codesourcery.com
prev parent reply other threads:[~2014-10-02 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 21:38 Doug Evans
2014-09-25 10:09 ` Phil Muldoon
2014-09-25 15:18 ` Paul_Koning
2014-09-25 21:29 ` Phil Muldoon
2014-09-25 22:07 ` Doug Evans
2014-10-01 18:10 ` Phil Muldoon
2014-10-02 22:11 ` Stan Shebs [this message]
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=542DCD9B.9010400@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.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