Re: GNATing ada files with the wrong extensions.

[Ted Dennison<dennison@telepath.com>]

In article <GIHGrs.Gnt@news.boeing.com>, Dale Pennington says...
>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.

Hmmmm. That seems simple enough, it ought to be worth attempting to put in when
the sources make it to the GCC baseline one fine day. 

But you do realise that there is more to the convention than that, don't you?
For instance, everything has to have the same name as the unit name. Also, you
have to use "-" to replace the dot in child packages and separates. If you have
files from another system that was library based instead of source based, odds
are you have some files that don't quite match their unit names.

>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) ?

I made a script to do #2 once, but not from the method you used. It instead used
the AdaMagic-style ada.lib and unit.map files. At the time, I discovered that
Gnat had trouble with large amounts of pragma Source_File_Name's, but that was
years ago. It ended up being easier to just browbeat everyone into using Gnat's
naming convention. :-(

---
T.E.D.    homepage   - http://www.telepath.com/dennison/Ted/TED.html
          home email - mailto:dennison@telepath.com