On 01/20/2014 08:28 PM, Andre Majorel wrote: >> +.BR strtold () >> +functions are thread-safe with exceptions. >> +These functions can be safely used in multithreaded applications, >> +as long as >> +.BR setlocale (3) >> +is not called to change the locale. > The sentence is from the Oracle Solaris's manpages. > Is the requirement that all threads be in the same locale ? Or > that the thread that calls strtod() not use setlocale() at all ? > Or maybe that setlocale() not be called by anyone after threads > are created ? Or even that setlocale() not be used AT ALL by the > process ? > > It's not obvious to me which it is ! > > I think that a more specific wording would be useful. > In a locale other than the standard "C" or "POSIX" locales, these function may recognize additional locale-dependent syntax. When these functions and setlocale() are simultaneously called in multithreaded applications, these functions will not be thread safe. -- Best Regards, Peng -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
