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 19:42:32 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!news-hog.berkeley.edu!ucberkeley!nntp-relay.ihug.net!ihug.co.nz!west.cox.net!cox.net!p01!news2.central.cox.net.POSTED!53ab2750!not-for-mail Message-ID: <3D869692.3030805@telepath.com> From: Ted Dennison User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: The Dreaded "Missing Subunits" References: <1b585154.0209121449.ef12609@posting.google.com> <3D819EE7.3A69E5EB@praxis-cs.co.uk> <4519e058.0209160548.461cef27@posting.google.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 17 Sep 2002 02:42:31 GMT NNTP-Posting-Host: 68.12.51.201 X-Complaints-To: abuse@cox.net X-Trace: news2.central.cox.net 1032230551 68.12.51.201 (Mon, 16 Sep 2002 22:42:31 EDT) NNTP-Posting-Date: Mon, 16 Sep 2002 22:42:31 EDT Organization: Cox Communications Xref: archiver1.google.com comp.lang.ada:29057 Date: 2002-09-17T02:42:31+00:00 List-Id: Keith Thompson wrote: > The source file naming situation for C++ and Ada actually seems pretty Very generally, I'd agree. However, I'd say C++ multiplies the problem quite a bit due to several factors. For one thing, there are 3 types of files rather than 2: includes, code, and inline includes (or there are 2 or 4 types, depending on who you talk to). Also C++ compilers almost never try to enforce or encourage one standard or another. Build tools do sometimes encourage a subset, but rarely one particular scheme. So its generally up to the whims of the developers rather than the compiler toolkit designers. There are a whole lot more developers than there are compiler vendors, so this amounts to a conucopia of different file extension schemes one has to be prepared to deal with. Also this means that knowing what compiler you are using is no help. > similar. The C and Ada file naming conventions are also pretty > similar, except that C's conventions are more consistent. That depends on what you mean by "consistent". Across all compilers: yes. Within a single compilation enviroment: usually not. It should also be noted that even where C is *more* consistent, it still isn't consistent. File name and directory path issues can still throw you off, and there are people (typically well out of baseball bat reach) who don't follow the standard. Few compilers try to enforce it, so like much of C, it is really only a standard in peoples' minds. But without these Zen-like qualities, it just wouldn't be the C we all know and love, would it? :-)