Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!fletcher
From: Don_Lewine@dgc.ceo.dg.com
Newsgroups: comp.std.unix
Subject: POSIX vs SVID
Message-ID: <11188@cs.utexas.edu>
Date: 14 Aug 90 22:44:12 GMT
Sender: fletcher@cs.utexas.edu
Reply-To: std-unix@uunet.uu.net
Lines: 25
Approved: fletcher@cs.utexas.edu (Guest Moderator, Fletcher Mattox)

From:  Don_Lewine@dgc.ceo.dg.com

CEO summary:
I have been comparing SVID Issue 3 (for V.4) to IEEE Std 1003.1-1988. 
I noticed that the SVID specifies header files in the synopsis for 
various functions that are not required for POSIX.  For example,
POSIX says that setuid() requires that <sys/types.h> be included.  
The SVID requires that both <sys/types.h> and <unistd.h> be included.
 
Question: Is there anything wrong with this?  If I write a strictly
conforming application, can I include <unistd.h> for SVID 
compatibility even if POSIX does not require it?  Is there any 
problem with including "extra" header files (other than the obvious 
restrictions on the namespace)?
 
BTW, looking at the SVR4 code there is nothing in <unistd.h> that 
would require it to be included for setuid().  There do not seem to 
be any symbols in the header file that are prohibited.  However, this 
is a standards questions and reading the .h files is cheating!





Volume-Number: Volume 21, Number 30