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.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!wuarchive!rex!ames!ads.com!bhanafee
From: bhanafee@ADS.COM (Brian Hanafee)
Newsgroups: comp.lang.ada
Subject: Re: File name conventions for Ada units
Message-ID: <BNR%LN#@ads.com>
Date: 4 Oct 90 17:22:35 GMT
References: <2190@sparko.gwu.edu> <2152@enea.se> <2202@sparko.gwu.edu>
Sender: usenet@ads.com (USENET News)
Organization: Advanced Decision Systems, Mt. View, CA (415) 960-7300
List-Id: <comp.lang.ada>

In article <2202@sparko.gwu.edu> mfeldman@seas.gwu.edu () writes:
>
>Meridian AdaVantage for Unix will, I think, accept any filetype
>(but of course it must be supplied explicitly). I have not tried to
>break it, but it accepts ahny filetype I'd ever use for an Ada file...

Not quite.  Meridian (at least under Ultrix) is guilty of spitting
out tons (I don't even know how many) of intermediate files, each
with their own predefined extensions.  If you happen to name a file
with one of those (undocumented) extensions, it will fail.  Try
using the extension ".ils", for example.  It also does a very
simplistic job of generating object file names in its ".aux"
directory;  you have to be somewhat careful with units whose names
start with the letter 'b'.

Brian Hanafee