Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ucsd!sdcsvax!ucsdhub!hp-sdd!hplabs!analog!smith
From: smith@analog.UUCP (Tom Smith)
Newsgroups: comp.lang.c++
Subject: Re: filenames for C++
Message-ID: <179@ward.analog.UUCP>
Date: 25 Apr 88 19:37:32 GMT
References: <724@acornrc.UUCP>, <1531@dataio.Data-IO.COM> <1988Apr24.085957.8413@utzoo.uucp>
Organization: Analog Design Tools Inc., Sunnyvale, CA.
Lines: 25
Summary: Don't close include file door

In article <1988Apr24.085957.8413@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes:
> >	.C	??	AT&T
> >	.c	.h	Guideleines
> >	.cc	??	Gnu
> >	.cxx	.hxx	Advantage
> >	.cpp	.hpp	Zortech
> 
> There is no need for a new naming convention for header files, actually.
> Assuming sane programmers, C++ programs will contain only #includes
> referring to C++ header files (or C++-compatible C header files) and C
> programs will contain only #includes referring to C header files.

In order to utilize UNIX system include files in C++ programs without
porting them, one must be able to distinguish between a K&R external
declaration and an ANSI C/C++ function template.  Common UNIX header
files, such as stdio.h, are usually ported for us hapless software
writers and provided along with the compiler/translater.

A fair amount of effort is being put into maintaining as much backward
compatibility with both ANSI and K&R C as possible by the
compiler/translater writers, in order to speed porting and help the
language catch on a bit.  Some compilers/translaters, such as
Glockenspiel's C++ (a downstream version of AT&T that used the .cxx/.hxx
'convention'), will take different actions based on the header file suffix.

Thomas H. Smith  {hplabs, ucbvax!sun}!analog