From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>, djgpp-workers AT delorie DOT com
Date:	Sat, 22 Jul 2000 18:49:44 -0400
MIME-Version:	1.0
Subject:	Re: Bug in bash 2.03's handling of compound commands?
Message-ID:	<3979ECC8.18313.E9FC7@localhost>
In-reply-to:	<39799EF9.9F9D3E89@phekda.freeserve.co.uk>
X-mailer:	Pegasus Mail for Win32 (v3.12c)
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

> I think there may be a bug in bash 2.03's handling of compound commands.
> For instance, if 'bob' does not exist, then you'd expect $? to be set to
> 127 after trying to execute it. However, I found the following:
> 
> DJGPP: "(bob); echo $?" -> 0 displayed
> Linux: "(bob); echo $?" -> 127 displayed
> 

Hmm,
I get 127 from this snippet with both Bash 2.03 and Bash 2.04.

Mark

- Raw text -