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-19 13:24:40 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!sn-xit-03!sn-xit-06!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: The Dreaded "Missing Subunits" Date: Thu, 19 Sep 2002 15:25:12 -0500 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: <1b585154.0209121449.ef12609@posting.google.com> <3D819EE7.3A69E5EB@praxis-cs.co.uk> X-Newsreader: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3719.2500 X-Complaints-To: abuse@supernews.com Xref: archiver1.google.com comp.lang.ada:29196 Date: 2002-09-19T15:25:12-05:00 List-Id: Robert A Duff wrote in message ... >Anyway, this all seems rather convoluted. Why can't the >compiler/builder automatically determine which compilation units are in >which files? Why is a separate tool needed? And a separate file of >pragmas Source_File_Name to maintain? Janus/Ada essentially does this. But there is a chicken & egg problem. The Janus/Ada compiler doesn't care about naming conventions; only the make tool does. To help out the make tool, the compiler stores the source file names in the project when they are compiled. So, you can use any naming you want, and makes will work fine without any user intervention. The problem is the first compile for a piece of source. You can tell the make tool the naming convention you are using (within limits), but you have to tell the make tool any names that don't match the convention. That can get old when someone sends a bunch of files as a bug report without any obvious naming convention (such as the 8 character abbreviations noted earlier). One way to reduce this problem is to integrate this with the IDE (which is what Rational does, and what we'll do when (if ever) we rewrite the IDE). But I don't think it can be solved in general. >Furthermore, none of this mumbo-jumbo would be necessary at all, >if only all Ada compilers agreed on the file naming convention. I think that GNAT naming has become a de-facto standard, in that much of the code that you get is in that format. If you can't handle it, you get complaints from your customers. (Perhaps other vendors mileage may vary.) Randy Brukardt