Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uunet!hsi!stpstn!lerman
From: lerman@stpstn.UUCP (Ken Lerman)
Newsgroups: comp.lang.c
Subject: Re: A question on C programming style
Message-ID: <6788@stpstn.UUCP>
Date: 19 Apr 91 12:32:01 GMT
References: <1991Apr12.103621.8907@umiami.ir.miami.edu> <1991Apr13.013911.18151@athena.mit.edu> <12060@dog.ee.lbl.gov> <1848@bbxsda.UUCP>
Reply-To: lerman@stpstn.UUCP (Ken Lerman)
Organization: The Stepstone Corporation, Sandy Hook, CT 06482
Lines: 24

In article <1848@bbxsda.UUCP> scott@bbxsda.UUCP (Scott Amspoker) writes:
|>In article <12060@dog.ee.lbl.gov> torek@elf.ee.lbl.gov (Chris Torek) writes:
|>>Indeed.  One thing, for which I argued (and still will argue---it
|>>seems `right' to me) which is not standard, would tip the balance
|>>all the way:  I believe that `#include' should (always) have been
|>>defined as `read this if you have not already'.
|>
|>Turbo C has an option to do exactly that.
|>

Objective-C uses #import to mean `read this if you have not already'.
#include has its usual meaning (which is sometimes useful).

There remains the question of what does it mean to say a file has
already been included.  One with the same name?  With the same path
and name?  With the same inode (on the same file system)?  With the
same contents?

For (IMHO) reasons having to do with where searches take place when
the included files is expressed as "filename.h" (instead of
<filename.h>) importing files with the same name (ignoring the path)
only once seems to be the right answer.

Ken