mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Gabriel Ravier <>
To:, Markus Wichmann <>
Subject: Re: [musl] Difference in pthread behavior between glibc and musl
Date: Thu, 13 Jul 2023 20:49:14 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <ZLAl5zVHEr4tnMkY@voyager>

On 7/13/23 18:27, Markus Wichmann wrote:
> Am Thu, Jul 13, 2023 at 04:02:54AM +0200 schrieb Gabriel Ravier:
>> so I don't get you mean by 'It is not "explicitly recommended"':
> Reading comprehension, please! The sentence you quoted contains a
> condition; one that Rich already pointed out to you. The condition is
> not fulfilled; musl does not detect that the key is invalid, and
> therefore the entire thing is null for this implementation. Let alone
> that the sentence is in a section explicitly marked "informative" (as
> opposed to normative).
> Ciao,
> Markus

I know it's not normative - that doesn't seem like it would change 
anything given that regardless is a recommendation, not a requirement.

The explanation you've given does makes sense though - the wording seems 
oddly ambiguous, but that does seem to be what it's trying to say.

      reply	other threads:[~2023-07-13 18:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 19:19 Appelmans, Madeleine
2023-07-11 19:42 ` Markus Wichmann
2023-07-12  2:48 ` Rich Felker
2023-07-13  1:00   ` Gabriel Ravier
2023-07-13  1:50     ` Rich Felker
2023-07-13  2:02       ` Gabriel Ravier
2023-07-13 16:27         ` Markus Wichmann
2023-07-13 18:49           ` Gabriel Ravier [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:

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

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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