Date: Fri, 16 Aug 1996 21:37:04 +1000 From: Bruce Evans <bde@zeta.org.au> To: j@uriah.heep.sax.de, jkh@time.cdrom.com Cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-lib@freefall.freebsd.org, jkh@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: cvs commit: src/lib/libncurses lib_newterm.c Message-ID: <199608161137.VAA19635@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> > Why is this? sigaction() is Posix, signal() ain't.
>>
>> sigaction had unwonted side-effects.
Actually, signal() has wanted side effects.
>I don't trust you. ;-) signal()'s implementation is mainly based on
^^^^^^ completely
>sigaction(). So if the latter has unwanted side-effects for you that
>signal doesn't have, it's probably a programmer's error.
The only difference (under BSD) is that signal() sets SA_RESTART for
most signals. The set of such signals may be changed using
siginterrupt().
Under SysVish systems, signal() also sets SA_RESETHAND and SA_NODEFER
to give traditional unreliable signals. signal() should only be used
if you want traditional system-dependent behaviour, i.e., almost never.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608161137.VAA19635>