home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!agate!agate!matt
- From: matt@physics.berkeley.edu (Matt Austern)
- Newsgroups: comp.lang.c++
- Subject: Re: Survey: File Extension
- Message-ID: <MATT.92Dec13011012@physics.berkeley.edu>
- Date: 13 Dec 92 09:10:12 GMT
- References: <1gb1h0INNle2@tsavo.hks.com> <78146@hydra.gatech.EDU>
- <1992Dec12.014834.926@netcom.com>
- <WARSAW.92Dec12174801@anthem.nlm.nih.gov>
- Reply-To: matt@physics.berkeley.edu
- Organization: Lawrence Berkeley Laboratory (Theoretical Physics Group)
- Lines: 17
- NNTP-Posting-Host: physics.berkeley.edu
- In-reply-to: warsaw@nlm.nih.gov's message of 12 Dec 92 22:48:01 GMT
-
- In article <WARSAW.92Dec12174801@anthem.nlm.nih.gov> warsaw@nlm.nih.gov (Barry A. Warsaw) writes:
-
- > More important is consistancy within your project and compilers/tools
- > ought to be configurable to use just about any extension: .cc .cxx
- > .cpp .C whatever...
-
- This is only possible for certain operating systems. Two of the three
- operating systems that I use on a regular basis are case-insensitive,
- so .C isn't much of an option.
-
- But yes, I agree with these sentiments; this choice should be made by
- users, not compilers.
- --
- Matthew Austern Just keep yelling until you attract a
- (510) 644-2618 crowd, then a constituency, a movement, a
- austern@lbl.bitnet faction, an army! If you don't have any
- matt@physics.berkeley.edu solutions, become a part of the problem!
-