Xref: utzoo comp.lang.c:23435 comp.lang.c++:5290 gnu.g++:493
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!mtxinu!unisoft!hoptoad!hsfmsh!dumbcat!marc
From: marc@dumbcat.UUCP (Marco S Hyman)
Newsgroups: comp.lang.c,comp.lang.c++,gnu.g++
Subject: Re: A solution to the multiple inclusion problem
Message-ID: <118@dumbcat.UUCP>
Date: 28 Oct 89 20:19:22 GMT
References: <14240@well.UUCP> <2051@prune.bbn.com> <1088@odin.SGI.COM> <1011@cirrusl.UUCP>
Reply-To: marc@dumbcat.UUCP (Marco S Hyman)
Organization: MH Software, Hayward, Ca.
Lines: 17

In article <1011@cirrusl.UUCP> dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi) writes:
    In article <1088@odin.SGI.COM> shap@delrey.sgi.com (Jonathan Shapiro)
    writes:
    
    >   #include FRED_H
    
    Please be alert for problems.  K&R requires the token after the
    "#include" to be a filename enclosed in double quotes or angle
    brackets, not an arbitrary symbol.

And the C compiler shipped with System V/386 3.2 (ISC's flavor) coffs
(I couldn't help myself ;-) on that one -- At least it didn't like
#include __FILE__.  (Another reason to use gcc/g++).

--marc
-- 
// Marco S. Hyman		{ames,pyramid,sun}!pacbell!dumbcat!marc