This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 0/2] New strfrom functions
On Thu, 25 Aug 2016, Paul E. Murphy wrote:
> Should we redact wcstofN* from the list of new _Float128 API too? Or, is
> the existing wcsto* API sufficient reason to keep it?
I think that since wcstof etc. are non-deprecated functions for all
existing floating-point types, it's appropriate to add versions for
_Float128. And, likewise, for strtof128_l, wcstof128_l. Rather than
adding a wide-character function without precedent for it in a standard,
that's adding a _Float128 version of a non-deprecated API set (just like
we want clog10f128 when clog10 is a GNU API, j0f128 when POSIX only has j0
for double not float and long double, etc.). (And not having them
wouldn't actually save any space in the libraries for powerpc64le when you
get onto support for long double being binary128, because the
implementations of those functions would be needed anyway at that point to
be what you get when calling wcstold etc. for binary128 long double. And
you don't have the questions of how to define the API that arise for
wcsfrom*.)
WG14 reflector message 12851 (7 Mar 2013) said regarding wide-string
functions "I believe these were discussed but haven't found the rationale
for omitting them.". So there might be something in early minutes of the
floating-point group, but I don't think it affects adding those functions
as part of the GNU API.
--
Joseph S. Myers
joseph@codesourcery.com