This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Thread-, Signal- and Cancellation-safety documentation
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Torvald Riegel <triegel at redhat dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>, Rich Felker <dalias at aerifal dot cx>, Florian Weimer <fweimer at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Sat, 08 Jun 2013 11:11:48 -0400
- Subject: Re: Thread-, Signal- and Cancellation-safety documentation
- References: <orppym7okv dot fsf at livre dot home> <20130326064347 dot GL20323 at brightrain dot aerifal dot cx> <515AB073 dot 9000500 at redhat dot com> <20130402134325 dot GO20323 at brightrain dot aerifal dot cx> <CAHGf_=q=2sM0C5kLazsVWiRfRvO0NX-sDRX2-SfoJkkCix9vzQ at mail dot gmail dot com> <1368788825 dot 3054 dot 3182 dot camel at triegel dot csb> <ora9nrh1cz dot fsf at livre dot home> <1369592301 dot 16968 dot 3046 dot camel at triegel dot csb> <orehcoqm0d dot fsf at livre dot home> <1370363818 dot 16968 dot 11024 dot camel at triegel dot csb> <orsj0ur1nu dot fsf at livre dot home> <1370610034 dot 16968 dot 11295 dot camel at triegel dot csb>
On 06/07/2013 09:00 AM, Torvald Riegel wrote:
>> First of all, it's not clear that we're talking about current or future
>> standards.
>
> If we have a deficiency in the current standard, that presumably needs
> to be fixed, then we can do that now in what we provide to users, with
> the hope of later applying it to a future version of the standard. I
> don't see any problem here.
No. There is a big problem here.
The complexity of the topic is so high that a mistake on our part
could have us document something that is later incompatible with
Issue 8 of POSIX.
The consequence of an incompatibility with POSIX is so terrible
that what you argue is too risky a path to take.
Therefore I am strongly in favour of Alex's position which is to
use what language POSIX has, even if it not well defined, and to
improve the documentation.
This conversation should still happen. It should be about Issue 8,
and about what will go into the next version of the standard.
Understanding the problem from glibc's perspective is incredibly
important because it will help us align with POSIX and comment
intelligibly on Issue 8.
However, at that point it is no longer a discussion about Alex's
patch or his current work.
Cheers,
Carlos.