This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Discussion: Formalizing the deprecation process in GDB
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: "Dave Korn" <dk at artimi dot com>
- Cc: cagney at gnu dot org, gdb at sources dot redhat dot com
- Date: Fri, 08 Oct 2004 12:10:54 +0200
- Subject: Re: Discussion: Formalizing the deprecation process in GDB
- References: <NUTMEGfCrbreLDwdbWK000002ed@NUTMEG.CAM.ARTIMI.COM>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: "Dave Korn" <dk@artimi.com>
> Cc: "'Andrew Cagney'" <cagney@gnu.org>,
> <gdb@sources.redhat.com>
> Date: Thu, 7 Oct 2004 13:42:24 +0100
>
> I look for the internals docs! And complain bitterly when I can't
> find them
Please don't hesitate to complain here whenever you find missing or
outdated docs in GDB. Thanks!
> Since opinions are being invited, I'll just mention that I'm currently
> working on an internal version of gdb for which I'm having to up-port a
> 5.x-compatible backend to 6.x series. I sometimes find it *ever* so hard
> when faced with yet another deprecated__ this or obsoleted_ that to know
> what the new and approved replacement is
Andrew, should we have a section in gdbint.texinfo that lists obsolete
techniques and their modern replacements, with short examples of both
the old and new code, like we did for ui_* stuff?