Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!sun-barr!lll-winken!sundance.llnl.gov!jac
From: jac@sundance.llnl.gov (James Crotinger)
Newsgroups: comp.lang.c++
Subject: Re: best extension for C++ files
Message-ID: <67782@lll-winken.LLNL.GOV>
Date: 11 Sep 90 07:50:02 GMT
References: <907@zinn.MV.COM> <1845@cs.rit.edu> <3358@stl.stc.co.uk> <1990Sep08.094000.10269@virtech.uucp>
Sender: usenet@lll-winken.LLNL.GOV
Organization: Lawrence Livermore National Laboratory
Lines: 19

The problem is that a program might be composed of both C and C++ code
and so it may be important for the compiler to distinguish between
rules for .c->.o and .cp->.o (.cp or .cc being my favorite choices
for C++ extensions). 

I don't see a problem with retaining .h for C++ header files, aside
from name conflicts (String.h and ANSI string.h, for example), but
the latter isn't a C++ specific problem. As long as the C++ and C
compilers look in the proper places for the C++ and C system include 
files, having both use .h shouldn't be a problem (and hasn't on 
either my Sun or my Amiga). 

  Jim

--
-----------------------------------------------------------------------------
James A. Crotinger   Lawrence Livermore Nat'l Lab // The above views 
jac@gandalf.llnl.gov P.O. Box 808;  L-630     \\ // are mine and are not 
(415) 422-0259       Livermore CA  94550       \\/ necessarily those of LLNL.