This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] Deprecate XM_FILE and TM_FILE


> Date: Mon, 13 Sep 2004 11:33:05 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: kettenis@gnu.org, brobecker@gnat.com, gdb-patches@sources.redhat.com
> 
> > It's about a point where something can be deprecated, and also about
> > the conditions that should be fulfilled for that.
> 
> I think this is progress, this discussion is finally focusing in on 
> specific concerns.

This was my intent from the beginning.  I'm glad that I finally
succeeded in explaining myself.

> >>> In the past, requests to not use old mechanisms have been [er]
> >>> declined
> > 
> > 
> > If such a request is declined, we can reject the patch.  I don't see a
> > problem here.
> 
> That is deprecation.
> 
> For us to reject such a patch we must have clearly, explicitly and 
> formally identify the mechanism as one that should not be used, and 
> recorded the decision in a way that both the patch reviewer and 
> contributor can quickly and efficiently access.

Fine.  All I ask for is to record the deprecation fact somewhere other
than in the code, until the 3 definitions are converted to use some
better mechanism.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]