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

Re: printf and POSIX compliance

X-seq: zsh-workers 18190
From: DervishD <raul@xxxxxxxxxxxx>
To: Stephane CHAZELAS <Stephane.CHAZELAS@xxxxxxx>
Subject: Re: printf and POSIX compliance
Date: Tue, 4 Feb 2003 19:26:11 +0100
Cc: zsh-workers@xxxxxxxxxx
In-reply-to: <20030204164425.A192@xxxxxxxxxxxxxxxxxx>
Mail-followup-to: Stephane CHAZELAS <Stephane.CHAZELAS@xxxxxxx>, zsh-workers@xxxxxxxxxx
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
Organization: Pleyades
References: <20030204164425.A192@xxxxxxxxxxxxxxxxxx>

    Hi Stephane :)

> http://www.opengroup.org/onlinepubs/007904975/utilities/printf.html
> that, according to POSIX:

    That is Single Unix Specification, not POSIX, am I wrong?

> 3- In addition to the escape sequences shown in the Base

    Oh, additional sequences, not POSIX ones. Ok, then :)

> Note that neither bash nor GNU printf behave better.

    The GNU printf says in its info manual that '\0ooo' is
interpreted as an octal number, but doesn's say anything about \ooo
where the 'o' are octal digits. It barfs in your example saying that
'\3' is not a valid escape sequence :(( I notified and got fixed a
bug about GNU printf argument handling a time ago, for not being SuS
compliant. Don't know the current status of SuS compliance that GNU
shell utilities have :??? Wait for GNU coreutils.

    BTW, as far as I know, zsh has not a printf builtin.

    Raúl

Follow-Ups:
- Re: printf and POSIX compliance
  - From: Stephane CHAZELAS

References:
- printf and POSIX compliance
  - From: Stephane CHAZELAS

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