This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH: Readline on MinGW


> Date: Thu, 28 Apr 2005 16:12:15 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Mark Mitchell <mark@codesourcery.com>, bug-readline@gnu.org,
> 	gdb-patches@sources.redhat.com
> 
> Could you give me a reference for this?  POSIX disagrees:
> 
>   http://www.opengroup.org/onlinepubs/009695399/functions/raise.html

Well, perhaps I misunderstand the language of Posix, but in this text:

  Otherwise, the effect of the raise() function shall be equivalent to calling:

  kill(getpid(), sig);

why did they use "Otherwise"?  To me, this says that `raise' is not
always the equivalent of `kill''.

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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]