comp.lang.ada
 help / color / mirror / Atom feed
From: cew@censun1.UUCP (SSUID Craig E Warsaw)
Subject: File name conventions for Ada units
Date: 28 Sep 90 20:25:46 GMT	[thread overview]
Message-ID: <589@censun1.UUCP> (raw)


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

             reply	other threads:[~1990-09-28 20:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1990-09-28 20:25 SSUID Craig E Warsaw [this message]
1990-09-29 16:29 ` File name conventions for Ada units stt
1990-09-29 22:04 ` Dan Rittersdorf
1990-10-01 14:56   ` David Emery
1990-10-06 14:37   ` Rik Palo
1990-09-30  2:49 ` Michael Feldman
1990-10-02 17:10   ` arny.b.engelson
1990-10-04 15:05     ` Michael Feldman
1990-10-02 21:55   ` Erland Sommarskog
1990-10-03  2:00     ` Alan Adamson
1990-10-03 17:00     ` Alex Blakemore
1990-10-04  9:37       ` Mike Harrison
1990-10-04 12:10       ` Robert Firth
1990-10-04  1:55     ` Michael Feldman
1990-10-04 17:22       ` Brian Hanafee
1990-10-08 17:33 ` Andy DeFaria
1990-10-11  8:59   ` Dan Bernstein
1990-10-12  5:29 ` Andy DeFaria
  -- strict thread matches above, loose matches on Subject: below --
1990-10-05 12:04 munck
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox