Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
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 15:00:00 -0000	[thread overview]
Message-ID: <3B56070E.90003@cygnus.com> (raw)
In-Reply-To: <20010718144735.B7843@nevyn.them.org>

> 
> I can't really think of a better name than target_signal.


Problem I have with ``target signal'' is that I'm never sure if I'm 
talking about a ``target signal'' or a ``target_signal''. 
``gdb_signal'' while contrived, is probably less ambigious.

One warped convention is to use ``siggnal'' [sic].  I don't know that 
that is any better than ``signals''.

	Andrew




  reply	other threads:[~2001-07-18 15:00 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
2001-07-18 15:00     ` Andrew Cagney [this message]
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=3B56070E.90003@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=dmj+@andrew.cmu.edu \
    --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