Re: g_printf_string_upper_bound (#50217)



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.

> 
> Regards,
>                                         Owen
> 

---
ciaoTJ





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]