Re: echo "enhancement" leads to confused legacy script tools...
From:
Andreas Schwab
Subject:
Re: echo "enhancement" leads to confused legacy script tools...
Date:
Mon, 20 Mar 2006 20:26:15 +0100
User-agent:
Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux)
Paul Eggert <eggert@CS.UCLA.EDU> writes:
> Andreas Schwab <schwab@suse.de> writes:
>
>> But note that bash interprets -n as an option, which is not compliant with
>> XSI.
>
> Bash doesn't claim conformance to XSI, so that's OK as far as Bash is
> concerned.
I understand that. It doesn't even conform to POSIX (in the default
configuration), since it also interprets -E and -e as options.
> There's a little history here. POSIX 1003.2-1992 said that echo has
> implementation-defined behavior if given any options, or if any
Are you sure about "any option"? The current spec only talks about -n.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."