From: "Mark E." <snowball3 AT bigfoot DOT com>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Tue, 4 Jul 2000 09:28:40 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: DJGPP problem executing a script
Message-ID: <3961AE48.6825.87F40@localhost>
References: <3961CA0E DOT 50A82A44 AT ecn DOT nl>
In-reply-to: <Pine.SUN.3.91.1000704160255.3385C-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

> By default, the backslashes in argv[0] of each DJGPP program are mirrored 
> to forward slashes by the startup code (unless you change that by running 
> stubedit).  So I still don't understand where did those backslashes come 
> from.

I did some debugging and the backslashes come from dosexec_find_on_path. When 
searches along PATH, it copies PATH but doesn't convert backslashes to 
forward slashes. So when script_exec searches for "perl", 
dosexec_find_on_path returns "c:\djgpp\bin/perl" because my PATH contains 
"c:\djgpp\bin".

As for why it isn't converted to forward slashes by perl's startup code, I 
can't answer that.

So perhaps the solution/workaround is instead to have dosexec_find_on_path 
always return slashes.