bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: echo "enhancement" leads to confused legacy script tools...


From: Eric Blake
Subject: Re: echo "enhancement" leads to confused legacy script tools...
Date: Tue, 28 Mar 2006 04:56:49 -0700
User-agent: Thunderbird 1.5 (Windows/20051201)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Paul Eggert on 3/20/2006 11:58 PM:
>>> 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.
> 
> Yes, I have the printed copy of POSIX 1003.2-1992, and it has
> different wording in this area.

POSIX 1003.1-2001 states on line XCU 12820 that "Implementations shall not
support any options."  When compiled for xpg (or using shopt -s xpg_echo),
both -e and -n should therefore be literal strings, not options.

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEKSSB84KuGfSFAYARAgAdAJ9+a44hUziPgLECYgtvGv9TAlxAfACfcQGx
0BvRfNt7iLLX5CLa4zkpq94=
=QQky
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]