This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Libiberty's snprintf for v3?
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- To: dj at redhat dot com
- Cc: gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, pcarlini at unitus dot it
- Date: Mon, 21 Apr 2003 23:02:42 -0400 (EDT)
- Subject: Re: Libiberty's snprintf for v3?
- References: <200304220052.h3M0qO830610@greed.delorie.com>
[second try, this time with a Subject:]
> From: DJ Delorie <dj at redhat dot 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 at caip dot rutgers dot edu