Date: Sat, 12 May 2001 13:19:01 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: tim DOT van DOT holder AT pandora DOT be
Message-Id: <1858-Sat12May2001131900+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com, snowball3 AT bigfoot DOT com
In-reply-to: <CAEGKOHJKAAFPKOCLHDIOEDOCDAA.tim.van.holder@pandora.be>
Subject: Re: spawn* and LFN again
References:  <CAEGKOHJKAAFPKOCLHDIOEDOCDAA DOT tim DOT van DOT holder AT pandora DOT be>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> Date: Sat, 12 May 2001 09:40:32 +0200
> 
> > > Basically, if I ask spawn to run <foo>, I expect it to run <foo> if it
> > > exists, and try <foo>.exe if it doesn't
> >
> > That's not what COMMAND.COM does.  Try typing "foo" in a directory
> > where both `foo' and `foo.exe' exist, and see who gets called.
> That's only because it doesn't consider foo executable.  I should amend it
> by saying it should try <foo> if it exists and is executable, and only try
> <foo>.exe afterwards.

But that's not what we want if `foo' is an unstubbed COFF: such
executables are run via go32-v2, which is both slower and has some
unpleasant side effects in subtle cases (the stack size and other
stubinfo fields are not always honored, command-line length is limited
to 126 characters, etc.).

So we actually have a good reason to look for foo.exe first.