X-Sybari-Trust: a45166c5 9ffcebbb cd1bde24 00000138
From: Martin Stromberg <eplmst AT epl DOT ericsson DOT se>
Message-Id: <200301211423.PAA03951@lws256.lu.erisoft.se>
Subject: Re: printf- & scanf-families: j, z, t qualifiers (C99) [PATCH]
To: djgpp-workers AT delorie DOT com
Date: Tue, 21 Jan 2003 15:23:36 +0100 (MET)
In-Reply-To: <E18az2s-0000sQ-00@phekda.freeserve.co.uk> from "Richard Dawe" at Jan 21, 2003 02:08:02 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Below is a patch to add support for the j, z and t conversion qualifiers
> to the printf- and scanf-families of functions.

Yummy! Thanks!

>   @port-note ansi The conversion specifiers @samp{F}, @samp{D}, @samp{I}, @samp{O}, and @code{U} are DJGPP extensions; they are provided for compatibility with Borland C and other compilers.  The conversion specifiers for the @code{long long} data type are GCC extensions.  The meaning of @samp{[a-c]} as a range of characters is a very popular extension to ANSI (which merely says a dash ``may have a special meaning'' in that context).
> + 
> + @port-note ansi-c99 The @code{hh}, @code{j}, @code{t} and @code{z} conversion specifiers first appeared in the ANSI C99 standard.

Just curious: those (two) lines above must be that long, I suppose?


Right,

						MartinS