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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6f9ac64c5319a5d9 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-22 16:20:40 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!dfw-service2.ext.raytheon.com.POSTED!not-for-mail Message-ID: <3B843E58.19BDAF@raytheon.com> From: Mark Johnson Reply-To: mark_h_johnson@raytheon.com X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.6-3.1smp i686) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: GNATing ada files with the wrong extensions. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 22 Aug 2001 18:20:56 -0500 NNTP-Posting-Host: 192.27.48.41 X-Complaints-To: news@ext.ray.com X-Trace: dfw-service2.ext.raytheon.com 998522439 192.27.48.41 (Wed, 22 Aug 2001 18:20:39 CDT) NNTP-Posting-Date: Wed, 22 Aug 2001 18:20:39 CDT Organization: Raytheon Company Xref: archiver1.google.com comp.lang.ada:12298 Date: 2001-08-22T18:20:56-05:00 List-Id: Dale Pennington wrote: > 1) run all the source code through GNATCHOP (or just a big rename script) to > get the GNAT naming convention. > > 2) create a gnat.adc file and fill it with a zillion Source_File_Name > pragma's. > > For reference I am using 3.13p at this time, and have read the docs. I was > kinda hoping that there was acutally a method to tell GNAT to treat .1.ada > as the same as .ads and .2.ada as the same as .adb. > > Am I missing something obvious, or are 1 and 2 my only options (and if so, > has anyone generated a godd script to perform #2) ? > No, nothing obvious for 3.13p. We have a large application as well - a couple million lines of code developed under Apex. Yes, we have a script that does the generation of source file name pragmas, one per directory. We have another script that assembles all of them into a monster file in the build directory. We don't use either much any more, but I could probably send you a copy. With the supported 3.14, we changed from #2 (big gnat.adc) to a two liner that basically is... pragma Source_File_Name (Spec_File_Name => "*.1.ada"); pragma Source_File_Name (Body_File_Name => "*.2.ada"); This works well for ALMOST all our code. We do have a couple vendors that provided files in GNAT naming conventions - what a pain. I could suggest alternative #3 - get a support contract from GNAT. [I know you'll like that suggestion Robert...] The new version of the compiler fixes this as well as lays in the framework for significant improvements for defining "a project". Part of the project stuff takes care of different naming conventions, directory structures, use of environment variables, and so on. --Mark (not an employee of ACT - but a user of their support)