This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: *wprintf and *wscanf requirement
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: jtc at acorntoolworks dot com, libstdc++ at gcc dot gnu dot org
- Date: Thu, 3 Mar 2005 15:21:10 -0600
- Subject: Re: *wprintf and *wscanf requirement
- Organization: Red Hat / Chicago
- References: <87d5ugmtcy.fsf@orac.acorntoolworks.com>
> I see that acinclude.m4 includes tests that disables libstdc++'s wide
> character support if the target doesn't support most of the wide char
> printf and scanf functions (it allows vfwscanf, vswscanf, and vwscanf
> to be omitted), but I haven't been able to find any instances where
> the library itself uses the functions. Did the library once use these
> C library functions for it's binary/ascii conversions, and when the
> library was changed to have it's own code the requirement not relaxed?
Yes. The wchar_t config is quite crufty.
I'm in the middle of cleaning up the wchar_t config. Part of this
involves pruning the list of functions that are going to be used.
I posted this last friday, but have been delayed for a bit with this.
You might want to wait until this is finished.
-benjamin