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.6 required=5.0 tests=BAYES_05,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!censun1!cew
From: cew@censun1.UUCP (SSUID Craig E Warsaw)
Newsgroups: comp.lang.ada
Subject: File name conventions for Ada units
Keywords: Ada, files, conventions, standards
Message-ID: <589@censun1.UUCP>
Date: 28 Sep 90 20:25:46 GMT
Organization: Century Computing, Inc., Laurel, MD
List-Id: <comp.lang.ada>


I'd like to start a discussion about file naming conventions
for ada units.  It would be ideal if people could quote from
any standards documents they are using.  The Ada Style Guide
used by NASA GSFC says nothing about file naming conventions.

I've been using the following (the convention used in my first
Ada class):

	package spec:	package_.ada
	package body:	package.ada
	subunit:	package__subunit.ada

I've also seen

	package spec:	package_spec.ada	or package_s.ada
	package body:	package_body.ada	or package_b.ada

By the way, there is an annoying aspect of all of these schemes.
If I use wildcarding to print or list files, all of the package
bodies occur before the package specs.  I'd prefer the specs
before the bodies, but that's not too important.

Thanks.

Craig Warsaw
Century Computing, Inc.
1014 West Street
Laurel, MD  20707
Internet:  cew@fox.gsfc.nasa.gov