Date:	Fri, 11 May 2001 13:23:45 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	"Mark E." <snowball3 AT bigfoot DOT com>
Message-Id:	<1190-Fri11May2001132345+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
In-reply-to:	<3AF9D983.25675.385587@localhost> (snowball3@bigfoot.com)
Subject:	Re: spawn* and LFN again
References:	<3AF8337A DOT 4152 DOT 2ADA56 AT localhost> <3AF9D983 DOT 25675 DOT 385587 AT localhost>
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

> From: "Mark E." <snowball3 AT bigfoot DOT com>
> Date: Wed, 9 May 2001 23:57:55 -0400
> 
> > What happens with lfnexe.bat.exe or lfnexe.foo.exe?
> 
> gcc -o lfnexe.bat.exe lfnexe2.c
> 
> >lfnexe.bat
> Bad command or file name

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
Windows 98) treats the dot specially here, probably because someone
left the old DOS logic intact.

However, if there are specific problems with what spawn* does, please
tell what they are.

- Raw text -