Sender: ml AT delorie DOT com
Message-ID: <34269008.3141386F@cdata.tvnet.hu>
Date: Mon, 22 Sep 1997 17:34:32 +0200
From: Molnar Laszlo <molnarl AT cdata DOT tvnet DOT hu>
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: DJGPP workers <djgpp-workers AT delorie DOT com>,
        Daisuke Aoyama <jack AT st DOT rim DOT or DOT jp>
Subject: Re: a patch for system()
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970914170712 DOT 20078B-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Eli Zaretskii wrote:
> > Now I use 2 character set, depending on whether the shell is unixy
> > (_is_unixy_shell()). I'm currently don't handle "..." specially because
> > most of us only use this to invoke djgpp programs, which will do the
> > globbing for themself.
> 
> No, that's wrong.  Arguments passed via `spawn' are NOT globbed by
> the child.  This was one of the significant changes in v2.01 that
> broke compatibility with v2.0.  The reason for the change was POSIX
> compliance: programs invoked through `exec' on Unix are NOT called
> via the shell, and, since globbing on Unix is done by the shell,
> arguments passed through `exec' aren't globbed.

I've tried this: 

	perl -e 'system ("ls ...");'

And it worked when SHELL was command.com, but didn't when SHELL was
bash. Why doesn't bash use djgpp's globbing? This is a BAD THING, IMHO.

Laszlo