Date: Wed, 25 Oct 2000 09:37:49 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Peter J. Farley III" <pjfarley AT banet DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Bash 2.04 beta 6a
In-Reply-To: <4.3.1.0.20001024211121.00ac9ac0@pop5.banet.net>
Message-ID: <Pine.SUN.3.91.1001025093713.7418B-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, 24 Oct 2000, Peter J. Farley III wrote:

> I thought the "#foo" in a double-quoted string might be being
> "substituted" as a perl variable whose value was null

Is that what really happens in the specific case where you saw the
problem?  I think it's really important to know what command was
passed to the shell, exactly, to be able to debug it efficiently.

Also, there are (at least) two more unknowns in this equation:

  - did Perl invoke Bash, COMMAND.COM, or our internal emulation of
    COMMAND.COM that is part of `system'?

  - do you have GNU Textutils installed where you saw this problem (if
    not, you get ECHO from COMMAND.COM)?

>  >You seem to be assuming that this is a Bash problem.  Why do you think
>  >that?  Does Bash 2.03 work with this example?
> 
> As for bash 2.03, the current development versions of perl will not 
> build or test at all with that version, which is why I switched to 
> v2.04.

You cannot build with Bash 2.03, but you surely could try that
specific case with it, no?