From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 23324 invoked from network); 7 Jul 2023 15:02:47 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 7 Jul 2023 15:02:47 -0000 Received: (qmail 13612 invoked by uid 550); 7 Jul 2023 15:02:44 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 13579 invoked from network); 7 Jul 2023 15:02:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688742152; x=1691334152; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=lu7BlkljyvJjQIbFTsYz/+qFJIr3yT32eZEDK9Vhhiw=; b=KtlZpQyRRk2v+glM78PzUN95xuWOb8nFUUTHrOp4fzd9bVYlmYq+fvbUXEXDhrj2VM I24vv9XqiY1zBHOopmxnjoAn5c4x6WBgCHsel5YsvgmZ8r2D0ErdwD63YKr+IhrG/vSn iWmw7eZ7hct+Plw3lljGQigYDTpYeTN29oV4drxukMc984xjTbW71Et77ORUmm5pZGEb xcdK0z8sKsIWIHXu/+kBvGhEkU3wAiZjldI5zUOtlyQTaa6HZNSKrVJNcHLyQ6kLzZRw cT+r+jGOOhoH/NwbUeGudCGKtN6ur9U8FTpewCzjtVTPmh83emc2/AriuCw0eDB3BV1H jsJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688742152; x=1691334152; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=lu7BlkljyvJjQIbFTsYz/+qFJIr3yT32eZEDK9Vhhiw=; b=IC/xxctyWxm4xWdlTGuED1LLQ4PETqJpyt+lltb/hDrUHWgEYzlQwK4x668ouX+G4Y k5Ld7FmY8TAxmPFAegwoBFM6cgsT0nylKx1dFK/EGONRlc0EuGCa4YfJEA5wg/m+YHFM DZqKRUiovx6d8QTa3Azo2TPQ8JRwZ5/PJLApM74KUPA8hokpilv8mwOdabPH7LJuXHcH QqhcqWbgxpn0bArgTBOD0SM3PrIWZoGn/9EHoMRuslXpQA9dYw48qExcMnpo506zXnFo rQX43CHLcdB42843kn8m41LXlHNll+pDxNmJF+CM1J7rw4vRTXdbEROP/XvN6yM1N5Rl x2Ug== X-Gm-Message-State: ABy/qLZ4AXLOcaBvgprWbTsZ32igUAbI1eHhS/Q6uIKwlJvRDLYInvsB /xQ2uYUJ1erF7pBlxqeswmgMg4pjDckzf1JsJAz0m9k0 X-Google-Smtp-Source: APBJJlHxt98nf7ZZwLPJ+HTXYrVJrrAgbRQk+a92XOP7soEAWXF0I+O6pI+cGg6trIKSyfeTznCt2MkpaZuMv4LS3JE= X-Received: by 2002:a05:651c:104b:b0:2b6:fe75:b8f3 with SMTP id x11-20020a05651c104b00b002b6fe75b8f3mr4111225ljm.29.1688742152044; Fri, 07 Jul 2023 08:02:32 -0700 (PDT) MIME-Version: 1.0 References: <309EDCC9-2402-46B5-BDBD-B96677E470DD@apple.com> <20230707124722.GE4163@brightrain.aerifal.cx> <054B1907-817E-496D-9F83-7FBE7AB0111A@apple.com> In-Reply-To: From: Andrew Bell Date: Fri, 7 Jul 2023 11:02:21 -0400 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="000000000000170e7005ffe6ec95" Subject: Re: [musl] __MUSL__ macro --000000000000170e7005ffe6ec95 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 7, 2023 at 10:19=E2=80=AFAM Markus Wichmann = wrote: > Am Fri, Jul 07, 2023 at 02:14:30PM +0100 schrieb Alastair Houghton: > > This is a somewhat irrelevant distraction and I rather wish I hadn=E2= =80=99t > > mentioned that as an example of odd behaviour. I=E2=80=99m well aware = that > > you cannot copy or assign `pthread_mutex_t` values in general (and I > > understand the reasons why). > > > > Please can we instead focus on the issue of whether or not musl should > > have `__MUSL__` and `__MUSL_MINOR__`. > > > > The counter-examples are not irrelevant. That is precisely the point. > Nobody advocating for implementation identification macros has so far > given a valid reason to do so. > I think you can say this and still add the macros. Perhaps it's true that nobody has valid reasons, but the fact that it comes up repeatedly says that some people don't understand this or perhaps they have valid reasons yet to be considered. I guess I don't understand the opposition -- is there any downside to musl to having the macros defined, necessary or not? (I'm saying this as a minimalist, so I'm surprising myself here.) --=20 Andrew Bell andrew.bell.ia@gmail.com --000000000000170e7005ffe6ec95 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Jul 7, 2023 at 10:19=E2=80=AF= AM Markus Wichmann <nullplan@gmx.net= > wrote:
= Am Fri, Jul 07, 2023 at 02:14:30PM +0100 schrieb Alastair Houghton:
> This is a somewhat irrelevant distraction and I rather wish I hadn=E2= =80=99t
> mentioned that as an example of odd behaviour.=C2=A0 I=E2=80=99m well = aware that
> you cannot copy or assign `pthread_mutex_t` values in general (and I > understand the reasons why).
>
> Please can we instead focus on the issue of whether or not musl should=
> have `__MUSL__` and `__MUSL_MINOR__`.
>

The counter-examples are not irrelevant. That is precisely the point.
Nobody advocating for implementation identification macros has so far
given a valid reason to do so.

I think = you can say this and still add the macros.

Perhaps= it's true that nobody has valid reasons, but the fact that it comes up= repeatedly says that some people don't understand this or perhaps they= have valid reasons yet to be considered.

I guess = I don't understand the opposition -- is there any downside to musl to h= aving the macros defined, necessary or not? (I'm saying this as a minim= alist, so I'm surprising myself here.)

--
Andrew Bell
andrew.bell.ia@gmail.com
--000000000000170e7005ffe6ec95--