From: i262jq@0w.se
To: musl@lists.openwall.com
Subject: Re: [musl] __MUSL__ macro
Date: Fri, 7 Jul 2023 17:05:59 +0200 [thread overview]
Message-ID: <ZKgp17c9A/u9Ml0K@localhost> (raw)
In-Reply-To: <054B1907-817E-496D-9F83-7FBE7AB0111A@apple.com>
On Fri, Jul 07, 2023 at 02:14:30PM +0100, Alastair Houghton wrote:
> issue of whether or not musl should have `__MUSL__` and `__MUSL_MINOR__`.
Introducing such macros would allow and encourage reliance on
implementation details instead of following the standards.
This means encouraging non-portable programming.
I think this already have been said on this list.
In other words, the question is not whether a change would make sense
for specific cases, but whether the effect on the _rest_ of the usage
of the library would be acceptable.
IMHO the effect would be to undermine portability and maintainability
in the long run, for yet unknown / unlimited set of softwares to be
maintained or written in the future.
Kudos to musl developers for a firm stance against misfeatures, also
ones which non-portable (possibly _right now and here_ attractive)
solutions would have a use for.
/i262jq
prev parent reply other threads:[~2023-07-07 15:06 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
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 [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:
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=ZKgp17c9A/u9Ml0K@localhost \
--to=i262jq@0w.se \
--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).