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.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Path: utzoo!attcan!uunet!seas.gwu.edu!mfeldman
From: mfeldman@seas.gwu.edu (Michael Feldman)
Newsgroups: comp.lang.ada
Subject: Re: File name conventions for Ada units
Keywords: Ada, files, conventions, standards
Message-ID: <2204@sparko.gwu.edu>
Date: 4 Oct 90 15:05:43 GMT
References: <589@censun1.UUCP> <2190@sparko.gwu.edu> <1990Oct2.171010.28845@cbnewsl.att.com>
Reply-To: mfeldman@seas.gwu.edu ()
Organization: The George Washington University, Washington D.C.
List-Id: <comp.lang.ada>

In article <1990Oct2.171010.28845@cbnewsl.att.com> arny@cbnewsl.att.com (arny.b.engelson) writes:
> 
>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.

Agreed. We can go too far with trying to impose a standard. But I still
_local_ or project standards are a very good idea, and I am annoyed that
there are compilers around that refuse to let me do that, or impose
arbitrary file extensions on me. I wonder if anyone from Verdix could 
respond here, and at least let us know why they do it. If TeleSoft and
Meridian (under Unix) can accept my file extensions why can't VADS?
Indeed, an earlier version of VADS _could_ do it. What's up?

Mike Feldman
it in an earlier version),