site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Nov 27, 2004, at 8:01 PM, Igor Shmukler wrote: Helping out someone is great. You are a nice person. --Matt _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... you are using (".c" for C; ".cc" or ".cpp" for C++; etc. There are generally well-accepted extensions for these files, so it makes sense to follow those conventions.) However, .cc is depricated. As far as I know standard says it has to be .cpp. In general a language standard covers naming format. Personally, I would just like you suggest to use plain-text. If vi(1) is not be happy with it, we cannot call this a real "C" source. The C++ standard, ISO/IEC 14882 (2003), does not say anything about the names of source files. This is left up to implementations. The GCC compiler accepts a number of extensions, including .cc, .cpp, and .cxx. There's no reason, other than personal preference or your organization's coding standards, to prefer one over another. (I do recommend against using .C, though. It's fine as far as GCC is concerned, but it interacts poorly with case-insensitive file systems.) This email sent to site_archiver@lists.apple.com