Article View: comp.std.unix
Article #1314Re: POSIX 1003.1 and <sys/types.h>
From: Chuck Karish
Date: Sun, 17 Dec 1989 21:06
Date: Sun, 17 Dec 1989 21:06
26 lines
1588 bytes
1588 bytes
From: karish@forel.stanford.edu (Chuck Karish) In article <479@longway.TIC.COM> uunet!cbnewsd.ATT.COM!jrstu (james.stuhlmacher,ih,) wrote: >From: jrstu@cbnewsd.ATT.COM (james.stuhlmacher) > >I was told by someone that the POSIX standard does not allow >including <sys/type.h> in any of the other include files such as ><grp.h>. Is this true? I could not find this anywhere in the book. >If it is true, why is this the case? Is this necessary? A portable application that uses <grp.h> had better #include <sys/types.h> itself anyway, so it will have type gid_t available on an implementation that does not use the nested #includes. There's no specific prohibition in the standard. However, it's a non-trivial task to implement the headers in such a way that this is safe. The implementation must not surprise the programmer by providing an unexpected typedef or function prototype that could legally be coded directly into a program. Chuck Karish karish@mindcraft.com (415) 323-9000 karish@forel.stanford.edu Volume-Number: Volume 17, Number 107
Technical Details
Message-ID:
<480@longway.TIC.COM>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!longway!std-unixReferences:
<479@longway.TIC.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!longway!std-unix From: karish@forel.stanford.edu (Chuck Karish) Newsgroups: comp.std.unix Subject: Re: POSIX 1003.1 and <sys/types.h> Keywords: POSIX <sys/types.h> Message-ID: <480@longway.TIC.COM> Date: 17 Dec 89 21:06:27 GMT References: <479@longway.TIC.COM> Sender: std-unix@longway.TIC.COM Reply-To: karish@forel.stanford.edu (Chuck Karish) Organization: Mindcraft, Inc. Lines: 26 Approved: jsq@longway.tic.com (Moderator, John S. Quarterman)