Problem with snprintf()
Wed Aug 9 11:18:00 GMT 2000
Egor Duda wrote:
> Wednesday, 09 August, 2000 Chris Faylor firstname.lastname@example.org wrote:
> >>>So snprintf() should always add a terminating \0.
> >>And snprintf() may return -1 only in case of encoding error, not if the
> >>string exceeds `size'. So that is answered as well, IMO.
> CF> So, have we come up with a patch for this behavior?
> i've posted one in http://sources.redhat.com/ml/newlib/2000/msg00183.html
> i believe it'll make (v)snprintf C99-compliant
> if there're no objections, will somebody kindly check it in?
> Egor. mailto:email@example.com ICQ 5165414 FidoNet 2:5020/496.19
I posted a patch yesterday. It fixes the problem plus it also handles the
case whereby size is 0 (writes nothing and allows a null pointer to be
-- Jeff J.
More information about the Newlib