Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!ocsmd!zeus!van
From: van@zeus.ocs.com (Van Gale)
Newsgroups: comp.unix.sysv386
Subject: Re: POSIX and ISC 2.2.x -- how many people are using this?
Message-ID: <1219@ocsmd.com>
Date: 25 Apr 91 02:27:22 GMT
References: <1991Apr14.193335.26288@ddsw1.MCS.COM> <1991Apr16.235122.26807@scuzzy.in-berlin.de> <1991Apr19.215401.1501@am.sublink.org> <1991Apr23.204602.14556@scuzzy.in-berlin.de>
Sender: news@ocsmd.com
Organization: Online Computer Systems, Germantown MD
Lines: 17

In an article (Heiko Blume) shows an example of posix job control:
>    sigset_t oldmask, newmask;
>    sigemptyset(&oldmask);		/* must initialize */
>    sigemptyset(&newmask);
>    sigaddset(&newmask, SIGCHOKE);	/* add signal to set */
>    sigprocmask(SIG_BLOCK, &newmask, &oldmask);

I haven't been able to read the standard but I assumed (from looking
at a sigprocmask man page) that it wasn't *really* necessary to
initialize oldmask with a call to sigemptyset since sigprocmask is
supposed to return the original mask there.

Does the standard issue a good reason for doing this anyway?

----
Van Gale
van@ocsmd.ocs.com