On Wed, Jan 08, 2003 at 04:13:50PM -0500, Daniel Jacobowitz wrote:
On Wed, Jan 08, 2003 at 04:03:33PM -0500, Andrew Cagney wrote:
>
> >Besides: this is why you should _remove_ them, rather than just
> >commenting them, if you want them to go away.
>
> The implication here being that I'm not removing deprecated code?
A heck of a lot slower than you're deprecating! There are now over
1200 references to deprecated constructs in GDB. That's just a rough
estimate, mind.
I understand why release branches are bad points to compare against for
this, but since I have several handy:
~150 deprecated references in gdb 5.3
~30 in gdb 5.2
> The simple reality is that it is not possible for a single individual
> remove all the old code in a single hit. It takes a group of people
> co-operating, and it takes time.
I feel the need to add:
If you are deprecating things single-handedly, what group of people do
you expect to co-operate? It's a matter of cleaning up after yourself.
No one is trying to do anything single handedly. I'm just the luck one
that gets to follow through some of the dirty work (and put up with the
resultant flack :-).