Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!longway!std-unix
From: karl@IMA.IMA.ISC.COM (Karl Heuer)
Newsgroups: comp.std.unix
Subject: Re: ANSI vs POSIX on <sys/types.h>
Message-ID: <719@longway.TIC.COM>
Date: 7 Jun 90 15:21:45 GMT
References: <711@longway.TIC.COM> <712@longway.TIC.COM> <714@longway.TIC.COM> <717@longway.TIC.COM>
Sender: std-unix@longway.TIC.COM
Reply-To: karl@IMA.IMA.ISC.COM (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 18
Approved: jsq@longway.tic.com (Moderator, John S. Quarterman)

From:  karl@IMA.IMA.ISC.COM (Karl Heuer)

In article <717@longway.TIC.COM> From:  Doug Gwyn <gwyn@smoke.brl.mil>
>In article <714@longway.TIC.COM> From:  Andy Tanenbaum <ast@cs.vu.nl>
>>However, why do you urge not to put #include <sys/types.h> into <signal.h>
>>under protection of #ifdef _POSIX_SOURCE?
>
>Because I don't think that use of _POSIX_SOURCE should pollute the
>name space beyond the minimum required for POSIX.

In an earlier thread in this newsgroup, it was decided that this is in fact a
requirement of POSIX.  (Clarified in the Supplement, I believe.)  If the user
himself has not included <sys/types.h>, then the name `pid_t' is not reserved
to the implementation, and so it falls in the user's namespace.

Karl W. Z. Heuer (karl@ima.ima.isc.com or harvard!ima!karl), The Walking Lint

Volume-Number: Volume 20, Number 27