Date: Tue, 4 Jul 2000 16:05:24 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Teun Burgers <burgers AT ecn DOT nl>
cc: djgpp-workers AT delorie DOT com
Subject: Re: DJGPP problem executing a script
In-Reply-To: <3961CA0E.50A82A44@ecn.nl>
Message-ID: <Pine.SUN.3.91.1000704160255.3385C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Tue, 4 Jul 2000, Teun Burgers wrote:

> I think there is some interaction here with the following piece of
> code that is in djgpp/djgpp.c from perl-5.6.0. I Assume this
> is the same as in 5.00502. This piece of code is called
> very early in the perl main program.
> 
> void
> Perl_DJGPP_init (int *argcp,char ***argvp)
> {
>     char *p;
> 
>     perlprefix=strdup (**argvp);
>     strlwr (perlprefix);
>     if ((p=strrchr (perlprefix,'/'))!=NULL)
>     {
>         *p=0;
>         if (strEQ (p-4,"/bin"))
>             p[-4]=0;
>     }
>     else
>         strcpy (perlprefix,"..");
> }
> 
> here there is a test on the presence of a slash. argvp points to
> argv.

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.