From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18674 invoked from network); 19 Aug 2002 16:38:49 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Aug 2002 16:38:49 -0000 Received: (qmail 16701 invoked by alias); 19 Aug 2002 16:38:35 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5268 Received: (qmail 16674 invoked from network); 19 Aug 2002 16:38:30 -0000 Date: Mon, 19 Aug 2002 12:34:30 -0400 From: Chet Ramey To: raul@pleyades.net Subject: Re: read -s Cc: okiddle@yahoo.co.uk, zsh-users@sunsite.dk, chet@po.cwru.edu Reply-To: chet@po.cwru.edu Message-ID: <020819163430.AA60149.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-In-Reply-To: Message from raul@pleyades.net of Fri, 16 Aug 2002 13:30:43 +0200 (id <3D5CE263.mailMZ11Q4LG@viadomus.com>) > >> 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@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/