From: Alexandre Oliva <aoliva@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Rich Felker <dalias@libc.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Peng Haitao <penght@cn.fujitsu.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Adding reentrancy information to safety notes?
Date: Wed, 31 Dec 2014 07:38:20 -0200 [thread overview]
Message-ID: <orppb0dur7.fsf@livre.home> (raw)
In-Reply-To: <54A377B8.60802@redhat.com> (Carlos O'Donell's message of "Tue, 30 Dec 2014 23:12:40 -0500")
On Dec 31, 2014, "Carlos O'Donell" <carlos@redhat.com> wrote:
> That is not the definition of reentrancy that I had in mind.
Since reentrant is such an overloaded term, how about using the term
Recursion-Safe, that AFAICT covers only the concept you have in mind.
Another possible term that occurs to me is Synchronously Reentrant, to
indicate it doesn't cover asynchronous reentrancy out of signals or
multiple threads. We could then shorten it as SR-Safe.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer
next prev parent reply other threads:[~2014-12-31 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 15:45 Adding reentrancy information to safety notes? Carlos O'Donell
[not found] ` <54A2C8A6.9050100-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-30 19:53 ` Michael Kerrisk (man-pages)
2014-12-30 20:08 ` Carlos O'Donell
[not found] ` <54A30624.7070207-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-30 20:35 ` Michael Kerrisk (man-pages)
2014-12-30 22:55 ` Alexandre Oliva
[not found] ` <ork318eoj4.fsf-o1YuAO9g/txBDLzU/O5InQ@public.gmane.org>
2014-12-30 23:05 ` Rich Felker
[not found] ` <20141230230529.GT4574-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2014-12-31 1:43 ` Alexandre Oliva
2014-12-31 4:12 ` Carlos O'Donell
2014-12-31 9:38 ` Alexandre Oliva [this message]
[not found] ` <orppb0dur7.fsf-o1YuAO9g/txBDLzU/O5InQ@public.gmane.org>
2014-12-31 16:07 ` Carlos O'Donell
[not found] ` <54A41F36.5010800-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-01 7:11 ` Alexandre Oliva
2015-01-05 15:26 ` Carlos O'Donell
2015-01-05 23:21 ` Alexandre Oliva
2015-01-07 9:52 ` Michael Kerrisk (man-pages)
[not found] ` <54A377B8.60802-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-31 9:31 ` Alexandre Oliva
[not found] ` <ortx0cdv3c.fsf-o1YuAO9g/txBDLzU/O5InQ@public.gmane.org>
2014-12-31 15:26 ` Carlos O'Donell
[not found] ` <54A41595.4010007-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-01 7:05 ` Alexandre Oliva
2015-01-05 14:25 ` Carlos O'Donell
2015-01-01 0:19 ` Rich Felker
[not found] ` <20150101001905.GU4574-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2015-01-05 15:05 ` Carlos O'Donell
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=orppb0dur7.fsf@livre.home \
--to=aoliva@redhat.com \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=penght@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.