home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!uunet.ca!ohrd!twriter
- From: twriter@rd.hydro.on.ca (Timothy Writer)
- Subject: Re: Survey: File Extension
- Message-ID: <1992Dec14.205733.10157@rd.hydro.on.ca>
- Reply-To: twriter@rd.hydro.on.ca
- Organization: "Ontario Hydro - Research Division"
- References: <1gb1h0INNle2@tsavo.hks.com> <78146@hydra.gatech.EDU> <1992Dec12.014834.926@netcom.com> <WARSAW.92Dec12174801@anthem.nlm.nih.gov>
- Date: Mon, 14 Dec 92 20:57:33 GMT
- Lines: 22
-
- 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...
-
- Good point. I'm writing some code which must be portatble between
- MS-DOS with MSC C/C++ 7.0 and IRIX (Silicon Graphics) with GNU
- g++-2.2.2. The only common extension is .cxx. Why is standardizing on
- a file extension important? Aren't there more serious standardization
- issues? Its trivial for compiler vendors to support all the popular
- extensions so why not do that and forget it?
-
- Just my $0.02.
- Tim
-
- --
- Tim Writer phone: (416) 231-4111 ext. 6990
- Ontario Hydro Research Division fax: (416) 237-9285
- Toronto, Ontario e-mail: twriter@rd.hydro.on.ca
- CANADA
-