Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Recursive #includes
Keywords: recursive includes
Message-ID: <9734@smoke.BRL.MIL>
Date: 27 Feb 89 16:31:00 GMT
References: <570@marob.MASA.COM> <9727@smoke.BRL.MIL> <573@marob.MASA.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <573@marob.MASA.COM> samperi@marob.masa.com (Dominick Samperi) writes:
>By the way, I couldn't find any comments about recursive includes in
>K&R, so I guess this means they are permitted?

K&R 1st Edition, Appendix A, Section 12.2:
	A compiler control line of the form
		#include "filename"
	causes the replacement of the line by the entire contents
	of the file "filename".  ...
	#include's may be nested.

That doesn't seem ambiguous to me.  "causes" should be read as
a requirement on the implementation.  "may" gives the programmer
specific license (in case there was any question).