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

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

On 01/22/2014 06:41 PM, Michael Kerrisk (man-pages) wrote:
>>> This wording can be interpreted to mean that calling setlocale()
>>> *is* permitted as long as the locale doesn't change. If that is
>>> really what you mean, then no further objections from me.
>>
>> That is what I mean.
> 
> Can I just confirm what I understand from this conversation:
> 
> * A call to strtod() is thread-safe so long as no other thread uses
> setlocale() to change the locale *during* the execution of strtod().
> * If a call to setlocale() changes the locale *before* a call to
> strtod(), then the call to strtod() is still thread safe.
> 
> Correct?
> 

Yes, it is correct.


-- 
Best Regards,
Peng

> Thanks,
> 
> Michael
> 
> 
>> --
>> Best Regards,
>> Peng
>>
>>> Otherwise, my recommendation would be
>>>
>>>   These functions can be safely used in multithreaded
>>>   applications, as long as setlocale() is not called during
>>>   their execution.
>>>
>>
> 
> 
> 

--
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