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!samsung!rex!uflorida!travis!danr
From: danr@SSD.CSD.HARRIS.COM (Dan Rittersdorf)
Newsgroups: comp.lang.ada
Subject: Re: File name conventions for Ada units
Summary: Convention used at Harris
Keywords: Ada, files, conventions, standards
Message-ID: <1110@travis.csd.harris.com>
Date: 29 Sep 90 22:04:48 GMT
References: <589@censun1.UUCP>
Sender: news@travis.csd.harris.com
Organization: Harris Computer Systems, Fort Lauderdale, FL
List-Id: <comp.lang.ada>

In article <589@censun1.UUCP> cew@censun1.UUCP (SSUID Craig E Warsaw) writes:
>
>I'd like to start a discussion about file naming conventions
>for ada units.
> ...
>
>	package spec:	package_.ada
>	package body:	package.ada
>	subunit:	package__subunit.ada

	This one seems awkward to me, personally, but personal taste is of less
	concern than being able to infer something about the contents of a file
	from it's name.

>
>I've also seen
>
>	package spec:	package_spec.ada	or package_s.ada
>	package body:	package_body.ada	or package_b.ada

	We use a scheme similar to this, except it doesn't have the annoying 
	attributes you mention below.

		package spec: package.a
		package body: package_b.a
		separate subunit: package_s.a

	The only thing that I would change here would be to name the subunit as
	well.  For example:

		package spec:       calendar.a
		package body:       calendar_b.a
		separate subunit:   calendar_local_time_s.a

	Unfortunately, there is no *written* standard to quote here -- this is a 
	defacto standard we use for naming units in the standard library which we
	release with HAPSE (Harris Ada Programming Support Environment).

>
>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.
>
	As you can see, this scheme avoids this annoying aspect.
	BTW, I personally feel the same way -- I like to see related files
	clustered together, and in a compilation order within the group.
	This scheme has the desired effect.

>Thanks.
>
	You're welcome.

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

-danr
______________________________________________________________________________
  Dan Rittersdorf  (Dan'l fer short...) : danr@travis.ssd.csd.harris.com
  Harris Corporation, Computer Systems Division, Fort Lauderdale, FL 33309
______________________________________________________________________________
  "Even a fool is thought wise if he keeps silent, 
     and discerning if he holds his tongue." --  Proverbs 17:28