Mail Archives: djgpp-workers/2001/05/12/04:02:23
> > > Then I think spawn*'s logic is better. It doesn't make sense, IMHO,
> > > to find a program lfnexe.foo.exe, but fail to find lfnexe.foo. If I
> > > replace the first dot with something else, as in lfnexe_foo, then both
> > > lfnexe_foo and lfnexe_foo.exe work. That is, COMMAND.COM (at least on
> > lfnexe.foo.exe would actually work; (for example, for hello.world.exe,
> > both 'hello.world' and 'hello.world.exe' run the executable).
>
> Not for me, it doesn't: I just tried (on Windows 98). If I type
> "hello.world [Enter]", it says "Bad command or file name". Only
> hello.world.exe works.
>
> You did try it from COMMAND.COM, yes?
Ho hum. *blush* Err, nope. I guess it was under 4DOS. COMMAND.COM indeed
fails to run hello.world. OK, in that case I think spawn should behave
like 4DOS.COM :-)
> > 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.
- Raw text -