home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!turing!coulin!arthur
- From: arthur@turing.ac.uk (Arthur van Hoff)
- Newsgroups: comp.lang.c++
- Subject: Re: Survey: File Extension
- Message-ID: <ARTHUR.92Dec18111030@morlich.turing.ac.uk>
- Date: 18 Dec 92 11:19:20 GMT
- References: <1gb1h0INNle2@tsavo.hks.com> <78146@hydra.gatech.EDU>
- <stanleyr.724172017@kramden> <Bz80Bu.HI4@knot.ccs.queensu.ca>
- Sender: usenet@turing.ac.uk (Usenet for nntp)
- Organization: The Turing Institute Ltd., Glasgow, Scotland
- Lines: 44
- In-Reply-To: kirkwood@qucis.queensu.ca's message of 13 Dec 92 23:09:30 GMT
-
-
- Hi,
-
- In article <Bz80Bu.HI4@knot.ccs.queensu.ca> kirkwood@qucis.queensu.ca
- (Scott Kirkwood) writes:
- > BTW: these are the extensions I've come across: .C, .c, .cxx,
- > .cp (Macintosh), .cpp, .cc, .c++, .C++, .h, .H, and .hxx (off the top
- > of my head).
-
- The "Rules and Recommendations" document for programming in C++ by
- Mats Henricson and Erik Nyquist of Ellemtel states that .hh should
- be used for headerfiles, .icc for files that contain inline methods
- and .cc for other source files.
-
- The .icc extentions seems to be missing from your list. A special extention
- for files that contain inline code is useful so that you can write the
- following to handle inline methods (from the above mentioned document):
-
- // AnyClass.hh
- #ifndef OUTLINE
- #include "AnyClass.icc"
- #endif
-
- // AnyClass.cc
- #ifdef OUTLINE
- #define inline
- #include "AnyClass.icc"
- #undef inline
- #endif
-
- Arthur van Hoff (arhtur@turing.com)
- --
-
- Arthur van Hoff
- The Turing Institute Limited
- 36 North Hanover Street,
- G1 2AD Glasgow, Scotland
-
- Tel: +44 41 552 8858 or +44 41 552 6400
- Fax: +44 41 552 2985
- Email: arthur@turing.com
-
- The opinions expressed in this message are not
- necessarily those of The Turing Institute Limited.
-