Xref: utzoo unix-pc.general:7132 comp.sys.att:11417
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!udel!princeton!jonlab!jon
From: jon@jonlab.UUCP (Jon H. LaBadie)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: 3B1 C runtime library bug; do you have it too?
Summary: Its not documented, ergo it is not a bug ;-)
Message-ID: <902@jonlab.UUCP>
Date: 8 Jan 91 14:09:55 GMT
References: <37567@cup.portal.com>
Followup-To: unix-pc.general
Organization: 4455 Province Line Rd., Princeton, NJ 08540
Lines: 23

In article <37567@cup.portal.com>, thad@cup.portal.com (Thad P Floryan) writes:

[ Bulk of article reporting erroneous results with printf specifiers

	%06.3f   and   %0*.*f

  is deleted ]

Thad reports that the 3B1 printf(3S) does not work as do other (most?)
printf's.  When given a field width begining with a 0, most printf's
will pad with spaces rather than blanks.

However, the Reference Manual supplied with the 3B1 makes no mention
of the use of a 0 in the field width.  Thus, the function is performing
as documented and this can not be considered a "bug".

Aren't semantics wonderful?  Maybe I could get a job at AT&T support ;-)

Jon

-- 
Jon LaBadie
{att, princeton, bcr, attmail!auxnj}!jonlab!jon