Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!mimsy!eneevax!umd5!brl-adm!adm!rbj@icst-cmr.arpa
From: rbj@icst-cmr.arpa
Newsgroups: comp.unix.wizards
Subject: section 3 manpages
Message-ID: <7574@brl-adm.ARPA>
Date: Thu, 28-May-87 16:13:04 EDT
Article-I.D.: brl-adm.7574
Posted: Thu May 28 16:13:04 1987
Date-Received: Sat, 30-May-87 11:25:51 EDT
Sender: news@brl-adm.ARPA
Lines: 27


   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!

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?

   For that matter, why are the include files organized as they are?  It
   seems to me that it would be much more intelligent for each .h file to
   look like

   #ifndef <identifier-unique-to-this-.h-file>
   #define <identifier-unique-to-this-.h-file>
    ...body of the .h...
   #endif

It would indeed. Do you volunteer?

	(Root Boy) Jim Cottrell	<rbj@icst-cmr.arpa>
	National Bureau of Standards
	Flamer's Hotline: (301) 975-5688

Uh-oh --  WHY am I suddenly thinking of a VENERABLE religious leader
frolicking on a FORT LAUDERDALE weekend?