Date: Tue, 18 Sep 2007 09:36:15 -0500 (CDT) From: "Sean C. Farley" <scf@FreeBSD.org> To: Bruce Evans <brde@optusnet.com.au> Cc: Xin LI <delphij@FreeBSD.org>, freebsd-standards@FreeBSD.org Subject: Re: vfprintf() string precision type Message-ID: <alpine.BSF.0.9999.0709180929550.57764@thor.farley.org> In-Reply-To: <20070918152516.T32708@delplex.bde.org> References: <alpine.BSF.0.9999.0709161922560.29967@thor.farley.org> <20070917152627.V29498@delplex.bde.org> <alpine.BSF.0.9999.0709171835400.56227@thor.farley.org> <20070918152516.T32708@delplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Sep 2007, Bruce Evans wrote: > On Mon, 17 Sep 2007, Sean C. Farley wrote: > >> On Mon, 17 Sep 2007, Bruce Evans wrote: > >>> From printf.3: >>> A field width or precision, or both, may be indicated by >>> an asterisk >>> .Ql * >>> or an asterisk followed by one or more decimal digits and a >>> .Ql $ >>> instead of a >>> digit string. >>> In this case, an >>> .Vt int > ^^^ >>> argument supplies the field width or precision. >> >> This is why I asked. The man page does not specifically state that >> the type must be int. At least in my head, "decimal digits" could be >> an integer of any size in base 10. The other quotes you give do >> specify it. Would it be acceptable to change the man page to state >> int type, so I do not ask again after I inevitably forget? :) > > Er, even the man page specifically says "int", using wording > essentially identical to C99. OK. I must be blind. Maybe, if we make it 24 font in bold with something before it saying "Sean, look here!", then I will actually see it. Watching after a toddler while reading, thinking or even breathing does not seem to work all that well. :) Sean -- scf@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.0.9999.0709180929550.57764>