linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ma Shimiao <mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cfree.3: ATTRIBUTES: Note function that is thread-safe
Date: Thu, 29 Jan 2015 06:55:38 +0100	[thread overview]
Message-ID: <54C9CB5A.7090007@gmail.com> (raw)
In-Reply-To: <54C98D65.9050100-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

On 01/29/2015 02:31 AM, Ma Shimiao wrote:
> Hello Michael,
> On 01/28/2015 07:05 PM, Michael Kerrisk (man-pages) wrote:
>>> +.BR attributes (7).
>>>> +.TS
>>>> +allbox;
>>>> +lb lb lb
>>>> +l l l.
>>>> +Interface	Attribute	Value
>>>> +T{
>>>> +.BR cfree ()
>>>> +T}	Thread safety	MT-Safe /* In glibc */
>> What is the "?* In glibc */" for?
> This page records different versions of cfree.
> Like cfree in SunOS 4, SCO OpenServer, glibc and so on.
> I just can confirm thread safety of cfree in glibc.
> So, I added a comment to help users understand which cfree 
> I'm declaring.
> 
> Did I miss something or any good ideas?

Oh -- I see what you mean, Ma Shimiao. I did not look at
the whole page--it's a strange page indeed, and your
choice seems reasonable.

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2015-01-29  5:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  6:09 [PATCH] cfree.3: ATTRIBUTES: Note function that is thread-safe Ma Shimiao
     [not found] ` <1422425343-20809-1-git-send-email-mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-01-28 11:05   ` Michael Kerrisk (man-pages)
     [not found]     ` <54C8C28F.2040107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-29  1:31       ` Ma Shimiao
     [not found]         ` <54C98D65.9050100-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-01-29  5:55           ` Michael Kerrisk (man-pages) [this message]

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=54C9CB5A.7090007@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@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).