comp.lang.ada
 help / color / mirror / Atom feed
From: arny@cbnewsl.att.com (arny.b.engelson)
Subject: Re: File name conventions for Ada units
Date: 2 Oct 90 17:10:10 GMT	[thread overview]
Message-ID: <1990Oct2.171010.28845@cbnewsl.att.com> (raw)
In-Reply-To: 2190@sparko.gwu.edu

In article <2190@sparko.gwu.edu>, mfeldman@seas.gwu.edu (Michael Feldman) writes:
> In article <589@censun1.UUCP> cew@censun1.UUCP (SSUID Craig E Warsaw) writes:
> >
[the DEC convention of pkg_.ada for spec, pkg.ada for body, pkg__unit for subs]

[the more common convention of pkg_s.ada for spec and pkg_b.ada for body]
 
> [VADS only accept ".a", and Irvine only accepts ".ada", how annoying]
> [extrapolating from Meridian's convention...
> I would go further and use .ads for a spec, .adb for a body, .ada for a
> main, and maybe .sub or whatever for a subunit. Why there are compilers, in
> this day and age, that limit file types to some predetermined value, is
> absolutely beyond me. At most there should be a default which can always
> be overridden.
> 
> Are others frustrated with these seemingly unjustifiable compiler limits?
> Can some compiler folks out there justify the limitations? Maybe I'm
> missing something here.
 
I agree that restrictions like Verdix and Irvine put on file types is
unacceptable.  But making Ada file types a standard, or even a uniform
convention, is not (IMHO) a good idea.  There are simply too many different
operating system file name formats still around.  Some limit file types to
3 characters, some (I think) still limit it to 1, others have no limit.
Overall file name length can be limited to 8, 14, or any number of chars.
It's easy to see where any one format could result in conflicts with other
tools in the environment that create files with the same extensions.  (The
".a" is an obvious example).  I don't want to lose my source code because
some CASE tool decides to create a file with the same name, especially in
UNIX where I don't have old versions.

Personally, I like the following:

    spec     body     main    subunit

  x_s.ada   x_b.ada   x.ada   x_subname_b.ada

Where "x" is the name of the compilation unit, which always ends in
"_pkg", "_task", "_proc", or "_func".  Of course, this works best when
file name length isn't limited (or you don't use subunits :-) ).

  -- Arny Engelson   att!wayback!arny

  reply	other threads:[~1990-10-02 17:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1990-09-28 20:25 File name conventions for Ada units SSUID Craig E Warsaw
1990-09-29 16:29 ` 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 [this message]
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