X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Thu, 25 Mar 1999 12:39:48 +0100 (MET)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Bash 2.03 update (March 19th)
In-Reply-To:	<199903250110.UAA01476@mescaline.gnu.org>
Message-ID:	<Pine.LNX.3.93.990325123346.16128A-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 24 Mar 1999, Eli Zaretskii wrote:

>    From: Michel de Ruiter  <mdruiter AT cs DOT vu DOT nl>
> 
>    - when `filename' is run, `filename.bat' has preference above
>      `filename'
> 
> Why do you think this is wrong?  I think this is the correct order (it
> has nothing to do with Bash, btw, it's due to  change in libc.a).

Sorry, I don't have all of the context for this one...

Just as an idea: in traditional DOS (i.e. command.com), program.bat is the
*last* thing that will be tried when you call 'program'. The command.com
search order is

   doskey macro (if any)
   in '.', and then in each directory of the PATH:
   {
	program.com
	program.exe
	program.bat
   }

So, if 'program' is a COFF binary, i.e. more like an .exe than a .bat,
then it should be tried before program.bat, IMHO. If it's a Bourne sh
script, I'ld still prefer trying it before the crippled .bat script.


Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -