From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/threads] Eliminate lin-lwp.c
Date: Thu, 16 Sep 2004 16:05:00 -0000 [thread overview]
Message-ID: <4149B92F.9080106@gnu.org> (raw)
In-Reply-To: <20040916154758.GA15671@nevyn.them.org>
> Er, why are you doing this? Why isn't it possible to have a separate
> target vector without moving all the code around?
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]).
Andrew
next prev parent reply other threads:[~2004-09-16 16:05 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 [this message]
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
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=4149B92F.9080106@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.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