delorie.com/archives/browse.cgi | search |
Message-Id: | <200007041521.RAA23029@cerbere.u-strasbg.fr> |
X-Sender: | muller AT ics DOT u-strasbg DOT fr |
X-Mailer: | QUALCOMM Windows Eudora Pro Version 4.0.2 |
Date: | Tue, 04 Jul 2000 17:15:09 +0200 |
To: | djgpp-workers AT delorie DOT com |
From: | Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr> |
Subject: | Re: DJGPP problem executing a script |
References: | <3961AE48 DOT 6825 DOT 87F40 AT localhost> |
<3961CA0E DOT 50A82A44 AT ecn DOT nl> | |
<3961AE48 DOT 6825 DOT 87F40 AT localhost> | |
Mime-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
>> So perhaps the solution/workaround is instead to have dosexec_find_on_path >> always return slashes. > >I think this would be too dangerous: __dosexec_find_on_path might be >used with programs that don't grok forward slashes, such as >COMMAND.COM. > >I think if we need to solve a local problem with scripts, it's >sufficient to solve it locally in script_exec. Wouldn't it be enough to just add a [perl] entry in djgpp.env that would do the backslash to forward slash convertion for PATH ? Pierre Muller Institut Charles Sadron 6,rue Boussingault F 67083 STRASBOURG CEDEX (France) mailto:muller AT ics DOT u-strasbg DOT fr Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |