Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!pasteur!ames!amdahl!pyramid!prls!philabs!pwa-b!mmintl!franka
From: franka@mmintl.UUCP (Frank Adams)
Newsgroups: comp.lang.c++
Subject: Re: filenames for C++
Message-ID: <2844@mmintl.UUCP>
Date: 29 Apr 88 16:37:17 GMT
References: <724@acornrc.UUCP> <1531@dataio.Data-IO.COM> <1988Apr24.085957.8413@utzoo.uucp> <179@ward.analog.UUCP>
Reply-To: franka@mmintl.UUCP (Frank Adams)
Organization: Ashton-Tate Corporation, East Hartford Development Center
Lines: 18

In article <179@ward.analog.UUCP> smith@analog.UUCP (Tom Smith) writes:
|In article <1988Apr24.085957.8413@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes:
|> 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.

Also, when using an intelligent editor, it is useful to be able to tell the
difference between C++ files and C files.  For example, when checking that
braces are matched, one needs to know what kind of comments are possible.
-- 

Frank Adams                           ihnp4!philabs!pwa-b!mmintl!franka
Ashton-Tate          52 Oakland Ave North         E. Hartford, CT 06108