mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alastair Houghton <ahoughton@apple.com>
To: musl@lists.openwall.com
Subject: Re: [musl] __MUSL__ macro
Date: Fri, 07 Jul 2023 16:34:37 +0100	[thread overview]
Message-ID: <829DB43D-E38A-4949-A0BE-B487279E4FC4@apple.com> (raw)
In-Reply-To: <ZKgtHM5qde3zeSOA@voyager>

On 7 Jul 2023, at 16:19, Markus Wichmann <nullplan@gmx.net> wrote:
> 
> Yes, it makes people write worse code. Not making the macros available
> makes people write more portable code, which is a good thing.

The people who would have misused the macros will simply find another way to detect musl that you’ll like even less (look at the Stack Overflow post we both mentioned; it’s literally the top answer).

Not making the macros available doesn’t stop people writing bad code, nor does making them available force anyone to write bad code.

Anyway, I’ve said enough on the subject.

Kind regards,

Alastair.


  parent reply	other threads:[~2023-07-07 15:35 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 [this message]
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=829DB43D-E38A-4949-A0BE-B487279E4FC4@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).