From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: *printf and zero size |
Date: | 2005-12-05 21:35:31 |
Message-ID: | 200512052135.jB5LZVs22806@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom, did you implement this functionality in *printf?
> > The size may be given as zero to find out how many characters are
> > needed; in this case, the str argument is ignored. Sprintf() and
> > vsprintf() effectively assume an infinite size.
>
> Where do you read that? The SUS says the opposite:
>
> If the value of n is zero on a call to snprintf(), an unspecified
> value less than 1 is returned.
>
> and that's what our code implements.
I got it from the BSD/OS manual page, and in the NetBSD manual page I
see:
If size is zero, nothing is written and str may be a NULL pointer.
and:
Upon successful completion snprintf() and vsnprintf() return the number
of characters that would have been written to a sufficiently sized str,
excluding the terminating NUL character.
but it seems this is some BSD'ism that we don't need to support if the
standard doesn't say so.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-12-05 21:40:57 | Re: *printf and zero size |
Previous Message | Tom Lane | 2005-12-05 21:05:58 | Re: *printf and zero size |