From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4c019ad9cc913bbe X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-09-16 06:48:50 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: dennison@telepath.com (Ted Dennison) Newsgroups: comp.lang.ada Subject: Re: The Dreaded "Missing Subunits" Date: 16 Sep 2002 06:48:50 -0700 Organization: http://groups.google.com/ Message-ID: <4519e058.0209160548.461cef27@posting.google.com> References: <1b585154.0209121449.ef12609@posting.google.com> <3D819EE7.3A69E5EB@praxis-cs.co.uk> NNTP-Posting-Host: 65.115.221.98 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1032184130 4055 127.0.0.1 (16 Sep 2002 13:48:50 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 16 Sep 2002 13:48:50 GMT Xref: archiver1.google.com comp.lang.ada:29024 Date: 2002-09-16T13:48:50+00:00 List-Id: Simon Wright wrote in message news:... > Robert A Duff writes: > > > The sad thing is that although Ada is very portable in many > > respects, the community of compiler vendors can't agree on > > file-naming conventions. Contrast with C, where everybody knows > > what .h and .c mean. > > Is this a joke? cos it's clear that .h and .c have absolutely _no_ > semantic content! (except, I suppose, that a compiler knows it's not It must be. The problem is that most folks *think* they know what those extensions mean, but the compiler could care less what you think. For instance, Tornado (the vxWorks development enviroment) comes with quite a few .c files that are "#include"d rather than compiled. Good luck figuring that out! And of course most folks feel that C++ should have its own extensions, but there is little agreement on what they should be. ".cpp" seems common, but I've also seen ".C" and ".cc". The extension ".c" is sometimes used to mean code that is purposely C compatable, while sometimes its used for C++-only files. For headers I've seen personally or seen suggested ".h", ".hpp", ".d", "..c", ".hh", and ".icc" (for inline header files). The C++ standard itself specifies that quite a few header files have no extension at all! Of course no matter what you use, the compiler won't care a bit, and will happily include a ".cpp" or compile a ".hpp", if you tell it to and the syntax passes. References: http://www.cs.umd.edu/users/cml/cstyle/