Re: [PATCH] strtod.3: ATTRIBUTES: Note functions that are thread safe with exceptions

[Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>]

On 01/21/2014 02:19 PM, Michael Kerrisk (man-pages) wrote:
>>> 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.
> 
> Hello Haitao,
> 
> So, do you think maybe a more precise wording would be better in 
> the man page?
> 

Maybe added simultaneously is better?

These functions can be safely used in multithreaded applications,
as long as setlocale(3) is not called to change the locale.

->

These functions can be safely used in multithreaded applications,
as long as setlocale(3) is not simultaneously called to change the locale.


-- 
Best Regards,
Peng

> Thanks,
> 
> Michael
> 
> 
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html