Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/threads] Eliminate lin-lwp.c
Date: Thu, 16 Sep 2004 20:29:00 -0000	[thread overview]
Message-ID: <20040916202905.GA26644@nevyn.them.org> (raw)
In-Reply-To: <4149F32F.6030807@gnu.org>

On Thu, Sep 16, 2004 at 04:10:23PM -0400, Andrew Cagney wrote:
> 
> >>>>>>>>>You mean add a "lin-lwp.h" which exports everything so that 
> >>>>>>>>>"linux-nat.c" can construct that vector, or conversly have 
> >>>>>>"linux-nat.h" >>>export everything so that "lin-lwp.c" can construct 
> >>>>>>the vector?
> >>>>>>>>>
> >>>>>>>>>Bleauh! Such a separation is artifical (although perhaphs the 
> >>>>>>single >>>file should be called inf-linux.[hc]).
> >>>
> >>>>>
> >>>>>
> >>>>>Yes, that's what I meant.  I'd like to preserve the revision history
> >>>>>when possible.
> >>
> >>>
> >>>The revision history or the existing files and their contents?  The 
> >>>former is always available in CVS.  The later, as I noted, is just an 
> >>>artifical separation that will complicate the objective of cleaning up 
> >>>this code.
> >
> >
> >I find the ability to use cvs annotate and diff on a function extremely
> >valuable, and you'll make that much more awkward if you move them
> >around without a reason.  I was asking if you had a reason to create
> >this inconvenience.
> 
> Yes, I want to avoid any artifical organization that will complicate the 
> objective of cleaning up this code.
> 
> What we need to preserve is the accumulated knowledge of bugs and 
> mis-implemented features - we do that by extending our test infrastructure.

I do not think that leaving these functions where they are will
complicate the process of cleaning them up.  Could you explain
why you see this as a problem?

> >>>I do see merit in creating an a new inf-linux.c (to be consistent with 
> >>>inf-ptrace, and inf-child), and I think I'll revise the patch to do that.
> >
> >
> >Please don't.  It's the native support for Linux.  By GDB's existing
> >conventions it ought to be linux-*.
> 
> linux-inf.c?  inf-linux.c is equally (if not more) consistent with the 
> new inf-ptrace.c and inf-child.c.

inf-* are currently more or less target agnostic; just "unixy".  GDB
convention says that native support for Linux - that's what this is -
belongs in linux-nat.c.  If some of it is left in lin-lwp.c for
historical reasons, that's a separate issue.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-09-16 20:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 15:36 Andrew Cagney
2004-09-16 15:48 ` Daniel Jacobowitz
2004-09-16 16:05   ` Andrew Cagney
2004-09-16 16:22     ` Daniel Jacobowitz
2004-09-16 16:32       ` Andrew Cagney
2004-09-16 17:38         ` Daniel Jacobowitz
2004-09-16 20:12           ` Andrew Cagney
2004-09-16 20:29             ` Daniel Jacobowitz [this message]
2004-09-16 21:13               ` Andrew Cagney
2004-09-16 21:25                 ` Daniel Jacobowitz
2004-09-16 22:23                   ` Andrew Cagney
2004-09-17 22:07                   ` Michael Snyder
2004-09-27 19:58 ` 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=20040916202905.GA26644@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /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