From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=3.0 tests=BAYES_00,FROM_ADDR_WS
	autolearn=no autolearn_force=no version=3.4.5-pre1
Date: 12 Jul 91 19:09:56 GMT
From: pa.dec.com!nntpd.lkg.dec.com!tle.enet.dec.com!brett@decwrl.dec.com  (bevi
n brett)
Subject: Re: Theft of valid program namespace!
Message-ID: <24320@shlump.lkg.dec.com>
List-Id: <comp.lang.ada>

In article <1991Jul12.172704.10258@phillip.edu.au>, x01233@phillip.edu.au write
s...

>Under Vax ada I am not allowed to create an executable from a  procedure
>named TT as it clashes with something Dec have allocated.
> 
>What is the LRM's attitude to this? Are companies allowed to 'steal' parts of 
>an Ada namespace when there is a clash? 
> 
>Dale.

Dale, you are clearly a novice VMS user.  This has *nothing* to do with VAX
Ada, and everything to do with VAX/VMS.

TT is a logical name defined by the system, to be [for historical RSX
compatibility], the terminal you are logged in on.

$ ACS LINK TT creates SYS$DISK:[]TT.EXE, and does so without any problems.

$ RUN TT tries to run the terminal, giving
%E, error opening TT:[BRETT.EG]*.*;* as input
%F, device is not file structured

It is clear from this error message that you tried to run TT:, rather than
SYS$DISK:[[]TT.EXE

$ RUN TT.EXE
will have the effect that you want.


VMS, unlike most other operating systems, has very detailed and explicit error
messages.  It is a shame that we have never managed to persuade people to read
them.

/Bevin

DIGITAL Ada project