linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Andre Majorel <aym-xunil-Bi/FLWfhfolQFI55V6+gNQ@public.gmane.org>
Cc: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
	aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] strtod.3: ATTRIBUTES: Note functions that are thread safe with exceptions
Date: Wed, 22 Jan 2014 16:57:38 +0800	[thread overview]
Message-ID: <52DF8802.6080501@cn.fujitsu.com> (raw)
In-Reply-To: <20140122082903.GE29966-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>


On 01/22/2014 04:29 PM, Andre Majorel wrote:
>>> If that is the case, how about :
>>>
>>>   These functions can be safely used in multithreaded
>>>   applications, as long as the locale is not changed during
>>>   their execution.
>>
>> The above sentence is OK, but I think added setlocale(3) is
>> better, thanks.
>>
>> These functions can be safely used in multithreaded
>> applications, as long as setlocale(3) is not called
>> to change the locale during their execution.
> 
> 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.
Thanks.


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

  parent reply	other threads:[~2014-01-22  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  8:15 [PATCH] strtod.3: ATTRIBUTES: Note functions that are thread safe with exceptions Peng Haitao
     [not found] ` <1390205712-10266-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-01-20 12:23   ` Michael Kerrisk (man-pages)
2014-01-20 12:28   ` Andre Majorel
     [not found]     ` <20140120122841.GC29966-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
2014-01-21  3:08       ` Peng Haitao
     [not found]         ` <52DDE4A6.5070405-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-01-21  6:19           ` Michael Kerrisk (man-pages)
     [not found]             ` <52DE1182.2030704-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-21  6:38               ` Peng Haitao
     [not found]                 ` <52DE15E2.2080607-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-01-21 13:52                   ` Andre Majorel
     [not found]                     ` <20140121135244.GD29966-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
2014-01-22  2:15                       ` Peng Haitao
     [not found]                         ` <52DF29C0.7080404-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-01-22  8:29                           ` Andre Majorel
     [not found]                             ` <20140122082903.GE29966-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
2014-01-22  8:57                               ` Peng Haitao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-22 10:41 Michael Kerrisk (man-pages)
     [not found] ` <CAKgNAkhCPtc4edgFhmc+3m+j_8AxucNzG4TY79sSuK2Cq8kreA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-23  0:07   ` Peng Haitao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52DF8802.6080501@cn.fujitsu.com \
    --to=penght-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
    --cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=aym-xunil-Bi/FLWfhfolQFI55V6+gNQ@public.gmane.org \
    --cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).