Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>,
	Mark Kettenis <kettenis@chello.nl>,
	gdb-patches@sources.redhat.com
Subject: Re: [rfa/i386] Make codestream deprecated?
Date: Wed, 08 Jan 2003 21:19:00 -0000	[thread overview]
Message-ID: <20030108211935.GA22170@nevyn.them.org> (raw)
In-Reply-To: <20030108211349.GA10113@nevyn.them.org>

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.

> Sure, it takes time.  Not all that much time, though; and it doesn't
> have to be done all at once.  I prefer to remove it from one target at
> a time and then remove support for it entirely.  There should be a
> reasonably close alternative available; after all, it's being
> deprecated in favor of something.
> 
> > If you look through the change log you'll notice that deprecated methods 
> > are being removed from the core of GDB, but the -tdep and -nat files are 
> > being left largely untouched.  Then, every so often, I or another 
> > maintainer will expunge the deprecated code from a target being it back 
> > into synck.  Over time the old code moves to the edges of gdb where it 
> > wilters and dies.
> 
> I don't see this happening.  I see it move to the edge of GDB where it
> withers, period.
> 
> To come back to the case at hand, this construct has already "moved"
> (started out?) to the edge of GDB.  Deprecating it isn't going to help
> it wither.
> 
> -- 
> Daniel Jacobowitz
> MontaVista Software                         Debian GNU/Linux Developer
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-08 21:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-01 16:39 Andrew Cagney
2002-12-01 17:02 ` Daniel Jacobowitz
2002-12-01 17:51   ` Andrew Cagney
2002-12-07 10:16 ` Mark Kettenis
2003-01-08 20:18   ` Andrew Cagney
2003-01-08 20:31     ` Daniel Jacobowitz
2003-01-08 21:03       ` Andrew Cagney
2003-01-08 21:13         ` Daniel Jacobowitz
2003-01-08 21:19           ` Daniel Jacobowitz [this message]
2003-01-08 22:43             ` Andrew Cagney
2003-01-30  3:31 ` Andrew Cagney

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=20030108211935.GA22170@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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