home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!darwin.sura.net!lhc!lhc!warsaw
- From: warsaw@nlm.nih.gov (Barry A. Warsaw)
- Subject: Re: Survey: File Extension
- In-Reply-To: twriter@rd.hydro.on.ca's message of Mon, 14 Dec 92 21:10:10 GMT
- Message-ID: <WARSAW.92Dec14165046@anthem.nlm.nih.gov>
- Lines: 20
- Sender: news@nlm.nih.gov
- Reply-To: warsaw@nlm.nih.gov (Barry A. Warsaw)
- Organization: Century Computing, Inc.
- References: <1gb1h0INNle2@tsavo.hks.com> <78146@hydra.gatech.EDU>
- <stanleyr.724172017@kramden> <Bz80Bu.HI4@knot.ccs.queensu.ca>
- <WARSAW.92Dec14101955@anthem.nlm.nih.gov>
- <1992Dec14.211010.10318@rd.hydro.on.ca>
- Date: 14 Dec 92 21:50:46 GMT
-
-
- me> Should the .h file extension matter? Do compilers supporting
- me> pre-compiled headers need to know the extension for header
- me> files? Just wondering 'cause we use .cc and .hh
-
- Timothy> Is there a good reason for having separate extensions for
- Timothy> C and C++ header files?
-
- Timothy> One situation where I have found it useful to have
- Timothy> separate extensions is for editors which choose a mode
- Timothy> based on the extension. However, I get around this with
- Timothy> GNU emacs using file local variables e.g.
-
- That's one reason, though as you mention the file local vars should
- handle that just fine. The other really is just notational. It helps
- our people to know if a header file is from some in-house package or
- not when they're looking at a #include list. .hh just seemed like it
- paralleled .cc nicely...
-
- It doesn't really have anything to do with #ifdef'ing on __cplusplus.
-