Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!decvax!ima!haddock!karl From: karl@haddock.UUCP (Karl Heuer) Newsgroups: comp.unix.questions Subject: Re: File extensions - final posting Message-ID: <296@haddock.UUCP> Date: Fri, 9-Jan-87 04:16:48 EST Article-I.D.: haddock.296 Posted: Fri Jan 9 04:16:48 1987 Date-Received: Fri, 9-Jan-87 22:47:19 EST References: <111@vianet.UUCP> <7462@utzoo.UUCP> <783@dg_rtp.UUCP> Reply-To: karl@haddock.ISC.COM.UUCP (Karl Heuer) Distribution: world Organization: Interactive Systems, Boston Lines: 11 Summary: "..c" is a C++ substitute for ".i" In article <783@dg_rtp.UUCP> meissner@dg_rtp.UUCP (Michael Meissner) writes: |In article <7462@utzoo.UUCP> henry@utzoo.UUCP (Henry Spencer) writes: |> Yet another convention, seen in some obscure places in the Unix sources: |> a file named, e.g., "foo..c" is a header file written in C. | |Or if you have C++ on your system, foo..c is the output of the C++ front |end that is then given to the regular C compiler to compile. Actually, foo.i is the "correct" name, but foo..c is often used because some versions of cc don't understand the .i suffix (though they will produce it). Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint