3B1 C runtime library bug; do you have it too?

[Jon H. LaBadie]

In article <37567 at cup.portal.com>, thad at 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