Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.UU.NET (Tom Neff)
Newsgroups: comp.lang.c
Subject: Re: source for included included files
Message-ID: <14647@bfmny0.UU.NET>
Date: 10 Sep 89 04:48:56 GMT
References: <9275@cbnews.ATT.COM> <14172@bloom-beacon.MIT.EDU> <1989Sep10.005745.23684@utzoo.uucp>
Reply-To: tneff@bfmny0.UU.NET (Tom Neff)
Organization: ^
Lines: 17
Summary:
Expires:
Sender:
Followup-To:

I have regularly been inconvenienced by various vendors' #include search
logic.  (Maybe "logic" is too strong a word. :-) )  Most recently I
slapped together a "temp compile" script for use under a client's "vi".
(No mail about EMACS please; I know, I know!)  I wrote the current file
to something in /tmp and ran that through "cc -S".  Boom, quoted
includes blew up.  Fortunately the -I switch in SV3.2 cc handles "x.h"
and not just <x.h> so that circumvented the problem in most cases; but
editing a file in another directory was tougher.

I think it was kind of stupid not to suggest some rules about what a
compiler should do IF directories exist in the host environment.  Even
where they don't, there's often a comparable concept (floppy drives,
account #s, volumes etc).  Real authors distributing real software have
to deal with junk like this.  Guidelines would be nice.
-- 
Annex Canada now!  We need the room,	\)	Tom Neff
    and who's going to stop us.		(\	tneff@bfmny0.UU.NET