Date: Wed, 18 Jun 2003 14:38:27 -0400 (EDT) From: Garrett Wollman <wollman@lcs.mit.edu> To: "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" <giffunip@yahoo.com> Cc: freebsd-standards@freebsd.org Subject: sigpause not POSIX compliant? Message-ID: <200306181838.h5IIcRQp042706@khavrinen.lcs.mit.edu> In-Reply-To: <20030618062913.65840.qmail@web13408.mail.yahoo.com> References: <20030618062913.65840.qmail@web13408.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Wed, 18 Jun 2003 08:29:13 +0200 (CEST), "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" <giffunip@yahoo.com> said: > sigpause appears as "obsoleted by sigsuspend" on our manpages > but it does apear on the UNIX API list: > http://www.unix-systems.org/version3/apis/t_8.html It actually is an obsolete interface, it's just not marked as such. sigsuspend() was introduced with the POSIX signal model and is a superior interface. Unfortunately, the merger between POSIX and SUS resulted in some of the old (and in some cases broken) SUS interfaces being introduced into POSIX for the first time (having been rightly rejected by SSWG in previous rounds). Our sigpause() does something completely different (hardly unsurprising), and expects an old 4.2-style signal mask rather than a single signal number. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306181838.h5IIcRQp042706>