-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You are right, I overstated my point. The .cpp suffix is one of several that identify a source file as a c++ program. The important point is that .c is not one of them. Sorry for the error. Thomas mentioned several suffixes he uses, all of which are shown as equivalent in the man page. But .c is not among them. There is the option to specify the language in a compiler option instead of in a file suffix. I wonder if some Makefile's use this, so it appears not to matter what the suffix is? On Thu, 1 Apr 2004, Luke Davis wrote: > On Thu, 1 Apr 2004, Chuck Hallenbeck wrote: > > > The GCC man page describes the various input file suffixes and > > their meanings. > > You would be talking about this part of the man page? > > Suffixes of source file names indicate the language and kind of pro- > cessing to be done: > > .c C source; preprocess, compile, assemble > .C C++ source; preprocess, compile, assemble > .cc C++ source; preprocess, compile, assemble > > If so, I'm not sure how that supports the statement, that "gcc requires > that C plus plus files should be named with a ".cpp" extension". > > Please elaborate. > > Luke > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > - -- The Moon is Waxing Gibbous (85% of Full) In a world without Fences or Walls no one needs Windows or Gates. My home page is now at http://www.mhcable.com/~chuckh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQCVAwUBQGyOODVdG8M9x9tGAQLmiAP/b3LAIbcC7XP1GcWaUi8cElrMfpZcp+Gb p8TIZ59Ijqkjx0sSnceff7BNe/ztzZPMnDEsl9OvpXBP2QcCvr/L6eG0lV0Imm+w ihz9DNqtqGR4xFpCzE26QYkbSetLlUsXECzFN+hVjGGtGZjOxsjgZX0+baIe0tQy yU66ygYdHog= =NNbP -----END PGP SIGNATURE-----
