From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: [musl] __MUSL__ macro
Date: Fri, 7 Jul 2023 17:19:56 +0200 [thread overview]
Message-ID: <ZKgtHM5qde3zeSOA@voyager> (raw)
In-Reply-To: <CACJ51z0riE9cbj5zoCXkEUX3Uust0WkYy7DA1OTnskjrj_27ZA@mail.gmail.com>
Am Fri, Jul 07, 2023 at 11:02:21AM -0400 schrieb Andrew Bell:
> 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.)
>
Yes, it makes people write worse code. Not making the macros available
makes people write more portable code, which is a good thing. Sometimes
people have to be made to think for a moment, and broken out of their
rut, to get them to do the right thing.
There is also the issue of what exactly the macros mean. Between
distribution patches and backports, a version number does not
necessarily map to a feature or bug set. And musl does not want to have
any quirks, it wants to just be a POSIX implementation. So what
specialties are supposed to be kept in mind when the musl macro is
defined? Keep in mind that __GNUC__ also does not just mean gcc anymore.
These things keep going off the rails all the time.
Ciao,
Markus
next prev parent reply other threads:[~2023-07-07 15:20 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
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 [this message]
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=ZKgtHM5qde3zeSOA@voyager \
--to=nullplan@gmx.net \
--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).