Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!linac.fnal.gov!allen From: allen@carob.ssc.gov (Mike Allen) Newsgroups: comp.lang.c++ Subject: Re: best extension for C++ files Message-ID: Date: 11 Sep 90 14:55:55 GMT References: <907@zinn.MV.COM> <1845@cs.rit.edu> <3358@stl.stc.co.uk> <1990Sep08.094000.10269@virtech.uucp> <67782@lll-winken.LLNL.GOV> Sender: news@linac.fnal.gov Reply-To: allen@sscvx1.ssc.gov Organization: SSC Laboratory, Dallas, TX Lines: 21 In-reply-to: jac@sundance.llnl.gov's message of 11 Sep 90 07:50:02 GMT We follow the Free Software Foundation's recommendations and use .h for header files and .cc for c++ programs. It is easy enough to make .h files work for both C and C++, wrapping them C++ specific stuff in #ifdef __cplusplus ... #endif. -- =============================================================================== Michael E. Allen SSC Laboratory MS-1046 2550 Beckleymeade Ave. Dallas, Texas 75237 (214)708-3031 allen@sscvx1.ssc.gov (Internet) allen@sscvx1 (Bitnet) SSCVX1::ALLEN (DecNet) But those who toiled knew nothing of the dreams of Those Who Planned; And the minds who planned the Tower of Babel Cared nothing for the workers who built it.