Message-Id: <4.3.1.0.20001026201738.00b1b3f0@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 26 Oct 2000 20:26:57 -0400
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: Re: Bash 2.04 beta 6a
In-Reply-To: <Pine.LNX.4.10.10010261304100.16093-100000@acp3bf>
References: <4 DOT 3 DOT 1 DOT 0 DOT 20001025221409 DOT 00ad89b0 AT pop5 DOT banet DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 01:14 PM 10/26/00 +0200, Hans-Bernhard Broeker wrote:
<Snipped>
 >But bash doesn't do it that way, not even in 'POSIXLY_CORRECT' mode. 
If
 >you want to echo a '#' sign after a whitespace, you have to quote it.

Understood.  What I still have to solve is how the invocation of bash 
under *ix systems differs from under DJGPP.

<Snipped>
 >No, that's documented standard behaviour of Bourne-style sh. '#' is a
 >comment character, in shell scripts. I suspect that Perl testsuite
 >fragment's goal was exactly that: to check which school the user's
 >shell is in.

You may be correct about that.  And I've already had to update the 
patch I made to prevent this DJGPP change from breaking the VMS perl 
version.

Thanks for the input.
---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)