Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcnc!rti!dg_rtp!meissner
From: meissner@dg_rtp.UUCP (Michael Meissner)
Newsgroups: comp.unix.wizards
Subject: Re: section 3 manpages
Message-ID: <2002@dg_rtp.UUCP>
Date: Sat, 30-May-87 15:24:22 EDT
Article-I.D.: dg_rtp.2002
Posted: Sat May 30 15:24:22 1987
Date-Received: Mon, 1-Jun-87 05:47:04 EDT
References: <7574@brl-adm.ARPA>
Reply-To: meissner@dg_rtp.UUCP (Michael Meissner)
Organization: Data General (Languages @ Research Triangle Park, NC.)
Lines: 22


		/* somebody else */
>    Why do so many of the man pages (eg inet(3N), the one which directly
>    prompted this posting) list the necessary include files to use the
>    routines in question, *except* that (almost?) NONE of them mention
>    <sys/types.h>, which is required by maybe half of them?  The only sure
>    way I've found to tell whether types.h is required is to try it!
> 

In article <7574@brl-adm.ARPA> rbj@icst-cmr.arpa (Root Boy Jim) writes:
> 
> Possibly because it is so common that it is included more often than not.
> Do you want every manual entry to mention <stdio.h> as well?

Now that you mention it, yes I do expect that every man page that refers
to stdio functions include <stdio.h>.  In the same vein, all string functions
should mention <string.h> (well, ok <strings.h> for BSD systems).  It's
things like this that make it painful to come up to speed in UNIX.
-- 
	Michael Meissner, Data General	Uucp: ...mcnc!rti!dg_rtp!meissner

It is 11pm, do you know what your sendmail and uucico are doing?