Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-readline@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Readline on MinGW
Date: Thu, 28 Apr 2005 22:13:00 -0000	[thread overview]
Message-ID: <je4qdqo8gx.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050428211735.GA17310@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 28 Apr 2005 17:17:35 -0400")

Daniel Jacobowitz <drow@false.org> writes:

>> In any case, it is traditional on Posix platforms to use `kill', not
>> `raise'.  I think the latter was introduced by ANSI/ISO C; if Readline
>> does not mandate an ISO C compiler like GDB does, it would make more
>> sense to use `raise' only if `kill' is unavailable.
>
> This isn't right.  POSIX mandates the existence of raise; ANSI/ISO C
> does not specify anything having to do with signals.

Both signal and raise together with a few signal numbers are part of ISO
C.  But the effect of signals is almost completely implementation-defined.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2005-04-28 22:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  6:53 Mark Mitchell
2005-04-28 20:09 ` Eli Zaretskii
2005-04-28 20:12   ` Daniel Jacobowitz
2005-04-28 20:45     ` Mark Mitchell
2005-04-28 21:02       ` Eli Zaretskii
2005-04-28 21:02       ` Chet Ramey
2005-04-29  0:44         ` Mark Mitchell
2005-04-29  7:31           ` Eli Zaretskii
2005-04-29 16:10             ` Christopher Faylor
2005-04-29  1:51         ` Mark Mitchell
2005-04-28 20:50     ` Eli Zaretskii
2005-04-28 21:17       ` Daniel Jacobowitz
2005-04-28 22:13         ` Andreas Schwab [this message]
2005-04-29  6:59         ` Eli Zaretskii

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=je4qdqo8gx.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=bug-readline@gnu.org \
    --cc=eliz@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