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!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!bu.edu!inmet!stt
From: stt@inmet.inmet.com
Newsgroups: comp.lang.ada
Subject: Re: File name conventions for Ada units
Message-ID: <20600066@inmet>
Date: 29 Sep 90 16:29:00 GMT
References: <589@censun1.UUCP>
Nf-ID: #R:censun1.UUCP:589:inmet:20600066:000:765
Nf-From: inmet.inmet.com!stt    Sep 29 12:29:00 1990
List-Id: <comp.lang.ada>


Re: file naming conventions.

We use:

    <unit-abbrev>.spc	--  Library unit spec
    <unit-abbrev>.bdy	--  Library unit body
    <unit-abbrev>.sub	--  Subunit
    <unit-abbrev>.dat   --  Body-less library package spec (data/types only)
    <unit-abbrev>.ada   --  Combination of spec and body
			      (Usually used for generics, spec-less subprogs,
			       and units exporting in-lined bodies)

    <unit-abbrev> is a shortening of the library-unit/subunit name
    to satisfy file-system length requirements.
    We have used these conventions with good success for > 500 K lines
    of Ada.  By the way, we try to minimize our use of subunits
    (refer to an earlier flame-battle on this subject!).

S. Tucker Taft
Intermetrics, Inc.
Cambridge, MA  02138