Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!wuarchive!udel!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: printf zero-pads strings?
Message-ID: <11390@smoke.BRL.MIL>
Date: 23 Oct 89 15:20:50 GMT
References: <7279@sdcsvax.UCSD.Edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <7279@sdcsvax.UCSD.Edu> williams@beowulf.UCSD.EDU (Paul Williamson) writes:
>Has the definition of printf changed since early drafts of the ANSI spec?

Yes, at one point the specs that had been derived from AT&T UNIX
System V specs were replaced with wording supplied by Alan Beale.
When we subsequently found unintended changes in behavior implied
in that version, additional revision occurred.  So far as I can
tell, the final fprintf() spec is exactly what we do intend.

>K&R2 and several other compilers give "    x", claiming that zero-padding
>applies only to numeric values.

And that is what we intend.