Libiberty's snprintf for v3?
Kaveh R. Ghazi
ghazi@caip.rutgers.edu
Tue Apr 22 03:02:00 GMT 2003
[second try, this time with a Subject:]
> From: DJ Delorie <dj@redhat.com>
>
> > But, on the upside we won't need vasprintf.c, and the resulting code
> > will probably be faster than the current implementation if we cache
> > the fd.
>
> File I/O is very expensive on Microsoft platforms (DJGPP, Cygwin,
> MinGW) compared to what you're used to under Unix platforms, even to
> /dev/null (both djgpp and cygwin emulate /dev/null, I don't know about
> mingw).
Ok, but that's only a concern if these platforms are missing
[v]snprintf and therefore would rely on the libiberty copy.
E.g. I'd expect that cygwin has snprintf. Don't know about the
others.
Can you please clarify the other platforms' situations?
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
More information about the Libstdc++
mailing list