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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e283979660f903f
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: test name clash on unix. was: GNAT 301a with Win95
Date: 1996/06/29
Message-ID: <dewar.836066565@schonberg>#1/1
X-Deja-AN: 163527050
references: <01bb5da2.dc327500$33668acd@iris.gomontana.com>
 	<31C94219.794BDF32@escmail.orl.mmc.com> <dewar.835359528@schonberg>
 <nhspbergdo.fsf_-_@paralysys>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-06-29T00:00:00+00:00
List-Id: <comp.lang.ada>


Nasser said

"Yes, good suggestions. Also one can add "." to the $path (edit
the .cshrc or .profile etc..) , make "." be the first in the path,
and when one invokes test, the shell will first look in . which is
the default current directory and use your "test" program , not the
one in /usr/bin ."

First, this does not work, at least in many systems, because test is
a shell command, not the name of something in /usr/bin, and thus
takes precedence over the path.

Second, putting . at the start of your path is not a good idea. In many
Unix environments, this practice is forbidden. The reason is that it is
a security risk, you can pick up unintended replacements for standard
system stuff this way, and a number of penetrations of Unix systems have
used this trick to get illicit information.