Re: Discussion: Formalizing the deprecation process in GDB

["Eli Zaretskii" <eliz at gnu dot org>]

> Date: Thu, 7 Oct 2004 11:01:21 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> Cc: 'Andrew Cagney' <cagney@gnu.org>, 'Eli Zaretskii' <eliz@gnu.org>,
> 	gdb@sources.redhat.com
> 
> I think that maintaining the list of deprecated features in a
> separate document is going to be a large amount of work.  GDB is
> changing so fast.

I don't see why it should be a large amount of work.  Features are
deprecated one at a time.  Each time a feature gets deprecated, all we
need is a short addition to the documentation stating (1) what is
being deprecated, and (2) an example of the old code using the
deprecated feature and a new code that should replace it.

This list will grow as more features are deprecated and OTOH
deprecated features that are deleted from the code will be deleted
from this list.

So where's that large amount of work you are afraid of?

> It's simpler to put that information directly
> in the code, and most of the time, the information is actually already
> there.

It maybe there, but there's no easy way to find it.