Re: [PATCH] latest ash has broken 'echo' command
On Thu, Oct 21, 1999 at 09:39:00PM +0200, Sven Rudolph wrote:
>
> Did we decide to follow Single Unix Specification. I thought we were
> on POSIX, and my draft allows -n (implementation defined).
If it's implementation defined that means echo is also allowed to not support
any options at all. So if you were going to write a script that should work
on all POSIX compliant shells, you must not use options and escape codes.
> According to rationale this compromise fulfills BSD and SYSV
> tradition.
I understand that.
> The Single Unix Specification explicitely forbids BSD heritage while
> it standardises the SYSV way.
Not really, unless POSIX enforces the options and escape codes, there is
no way to use them portably. So printf is still the way to go for escape
codes and -n.
PS Can someone please find the exact phrasing of POSIX on this matter?
--
Debian GNU/Linux 2.1 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Reply to: