Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: read -s

X-seq: zsh-users 5268
From: Chet Ramey <chet@xxxxxxxxxxxxxxxxx>
To: raul@xxxxxxxxxxxx
Subject: Re: read -s
Date: Mon, 19 Aug 2002 12:34:30 -0400
Cc: okiddle@xxxxxxxxxxx, zsh-users@xxxxxxxxxx, chet@xxxxxxxxxxx
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
Read-receipt-to: chet@xxxxxxxxxxx
Reply-to: chet@xxxxxxxxxxx

> >>     For example, bash has a non-POSIX, non-SuSv3 compliant
> >> implementation of 'printf' builtin
> >Out of interest, in what way is bash's printf non-compliant?
> 
>     The 'printf' builtin of BASH gives an error if you print, for
> example, '--'. It interprets it as an option given... SuSv3 says that
> printf must print whatever you pass as parameter.

This is not correct.

In http://www.opengroup.org/onlinepubs/007904975/utilities/printf.html:

The `OPTIONS' section of the printf description says `None'.

http://www.opengroup.org/onlinepubs/007904975/utilities/xcu_chap01.html#tag_01_11
describes what this means:

Default Behavior: When this section is listed as "None.", it means
that the implementation need not support any options.  Standard
utilities that do not accept options, but that do accept operands,
shall recognize "--" as a first argument to be discarded. 

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )

Chet Ramey, ITS, CWRU    chet@xxxxxxxxxxx    http://cnswww.cns.cwru.edu/~chet/

Messages sorted by: Reverse Date, Date, Thread, Author