| delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-workers-bounces using -f |
| Date: | Thu, 14 Feb 2002 12:21:38 +0200 (IST) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | Tim Van Holder <tim DOT van DOT holder AT pandora DOT be> |
| cc: | djgpp-workers AT delorie DOT com |
| Subject: | Re: Some small bash issues |
| In-Reply-To: | <1013672451.28939.34.camel@bender.falconsoft.be> |
| Message-ID: | <Pine.SUN.3.91.1020214121957.28394L-100000@is> |
| MIME-Version: | 1.0 |
| 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 |
On 14 Feb 2002, Tim Van Holder wrote:
> foo=bar ./shell-script
>
> because everything in the script is simply a 'new command'.
I fail to see the difference between
foo=bar ./script
and
foo=bar echo $foo
What is the difference here?
> foo=bar ./perl-script
>
> works fine (presumably, bash tries to process it as a shell script, sees
> the #!, expands the envvar, and hands the script off to the system).
> On DJGPP, bash runs the script without substituting the variable.
Why doesn't Bash expand the variable in the DJGPP port?
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |