From: Alastair Houghton <ahoughton@apple.com>
To: musl@lists.openwall.com
Subject: Re: [musl] __MUSL__ macro
Date: Fri, 07 Jul 2023 09:24:23 +0100 [thread overview]
Message-ID: <4A51E383-9AC5-4333-A5B7-29D9CBBE462B@apple.com> (raw)
In-Reply-To: <D9A8DBB2-C4E0-4F86-8DE8-EFC59818FF8D@Wilcox-Tech.com>
On 7 Jul 2023, at 08:30, A. Wilcox <AWilcox@Wilcox-Tech.com> wrote:
>
> My proposal obviates the need for a PREREQ-style macro because user-facing behavioural differences would be tracked by the monotonically increasing number. I suppose the next bikeshed would be determining when to increase and when not to, but I don’t think we should open that up here.
A single monotonically increasing number might be OK, though it does mean that there’s no way to signal a significant incompatibility by bumping the major number, depending on how the project chooses to manage versioning. (Basically, your monotonically increasing number is my minor version number here :-))
I also don’t understand why people doing stuff like this
https://stackoverflow.com/questions/58177815/how-to-actually-detect-musl-libc
is not seen as a problem. To my mind, it's *far* worse than having musl’s maintainers in charge of a macro definition (perhaps alongside documentation for it that explains that you usually shouldn’t use it, which could come with copious examples of how to avoid doing the wrong thing... I didn’t provide that in my patch, but if writing that is what it takes to get it accepted, I’m game).
Kind regards,
Alastair.
next prev parent reply other threads:[~2023-07-07 8:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 10:48 Alastair Houghton
2023-07-06 12:17 ` Alex Xu
2023-07-06 16:26 ` Szabolcs Nagy
2023-07-07 7:14 ` Alastair Houghton
2023-07-07 7:30 ` A. Wilcox
2023-07-07 8:24 ` Alastair Houghton [this message]
2023-07-07 11:20 ` Laurent Bercot
2023-07-07 11:45 ` Jeffrey Walton
2023-07-07 13:53 ` Rich Felker
2023-07-07 14:18 ` Alastair Houghton
2023-07-07 12:47 ` Rich Felker
2023-07-07 13:14 ` Alastair Houghton
2023-07-07 14:19 ` Markus Wichmann
2023-07-07 14:26 ` Markus Wichmann
2023-07-07 14:46 ` Alastair Houghton
2023-07-07 15:02 ` Andrew Bell
2023-07-07 15:19 ` Markus Wichmann
2023-07-07 15:24 ` Andrew Bell
2023-07-07 15:34 ` Alastair Houghton
2023-07-07 15:45 ` Rich Felker
2023-07-07 15:58 ` Alastair Houghton
2023-07-07 15:05 ` i262jq
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=4A51E383-9AC5-4333-A5B7-29D9CBBE462B@apple.com \
--to=ahoughton@apple.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).