From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] signals 1/3 - move target_signal handling out of target.c
Date: Wed, 18 Jul 2001 14:47:00 -0000 [thread overview]
Message-ID: <20010718144735.B7843@nevyn.them.org> (raw)
In-Reply-To: <3B55FC9C.3080306@cygnus.com>
On Wed, Jul 18, 2001 at 05:16:12PM -0400, Andrew Cagney wrote:
> > I've also got a few small cleanups that can go in after the code moves (I
> > want to keep them separate for revision history purposes).
>
>
> Very wise move.
See? I do learn :)
> > 2001-07-18 Daniel Jacobowitz <dan@debian.org>
> >
> > * signals.c: New file.
> > * target.c (struct signals): Move to signals.c.
> > * target.c (target_signal_to_name): Likewise.
> > * target.c (target_signal_from_name): Likewise.
> > * target.c (target_signal_from_host): Likewise.
> > * target.c (do_target_signal_to_host): Likewise.
> > * target.c (target_signal_to_host_p): Likewise.
> > * target.c (target_signal_to_host): Likewise.
> > * target.c (target_signal_from_command): Likewise.
> > * target.c (initialize_targets): Move check of
> > struct signals to...
> > * signals.c (_initialize_signals): Here. New function.
>
>
> No problems with the theory. I just wonder about the file name.
> A logical follow-on is to create ``signals.h'' (and put ``enum
> target_signal'' there). Anyone know of a potential conflict?
>
> If, in a later change there is going to be a
> s/target_signal/<something-sensible>/ should the file name reflect that
> intent.
I can't really think of a better name than target_signal. One change I
want to make eventually, but can not now, is to break the file up even
further to the parts which do and do not need <signal.h> - along with
this would be compiling the part that does need signal.h only when
native and doing something else otherwise. But that's a long way down
the road.
I don't know of any conflicts with "signals.h", but I'm not an
authority on such things. I'll wait a day or two and commit this (with
a proper changelog) unless someone expresses preference for another
name.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-07-18 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 11:07 Daniel Jacobowitz
2001-07-18 13:42 ` Eli Zaretskii
2001-07-18 14:43 ` Daniel Jacobowitz
[not found] ` <3B55FC9C.3080306@cygnus.com>
2001-07-18 14:47 ` Daniel Jacobowitz [this message]
2001-07-18 15:00 ` Andrew Cagney
2001-07-18 15:37 ` Daniel Jacobowitz
2001-07-19 11:09 ` Daniel Jacobowitz
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=20010718144735.B7843@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=ac131313@cygnus.com \
--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