Subject: Re: unistd.h vs signal.h and stdlib.h
To: Henry G. Juengst <juengst@saph5.physik.uni-bonn.de>
From: J.T. Conklin <jconklin@netcom.com>
List: current-users
Date: 02/13/1995 14:08:11
> I just found the following conflicts:

Hmm.  Is your application redefining const between where these header
files are included?  Some of those declarations are exactly identical
(getopt, getsubopt).

> May be the signal and getopt stuff should be removed from unistd.h
> and replaced by an include of signal.h and stdlib.h.

What header files a given header file may #include is restricted by 
the various standards (POSIX.1, ANSI, etc.) NetBSD tries to conform
to.  This is because those standards mandate what identifiers are
reserved when a particular header is included.  

	--jtc