Re: g_printf_string_upper_bound (#50217)

[Owen Taylor <otaylor redhat com>]

Tim Janik <timj gtk org> writes:

> On 26 Feb 2001, Owen Taylor wrote:
> 
> > Shawn T Amundson <amundson eventloop com> writes:
> 
> > Also, I'd really like to see g_strdup_printf() use vasprintf()
> > when available; it's going to be more space efficient, and I
> > suspect it will be faster, even if we have to g_strdup() afterwards
> > when g_malloc() isn't a direct wrapper of malloc().
> 
> iirc we aren't currently using it, because there were portability
> problems with vasprintf() not correctly reporting the number of
> characters in the resulting string.

I don't recall that. I seem to remember problems with the return
of sprintf(), but that's different.

vasprintf is a GNU libc extension, so portability scarcely comes
into it...
                                        Owen