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.3 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,T_SCC_BODY_TEXT_LINE
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 23470 invoked from network); 7 Jul 2023 15:06:33 -0000
Received: from second.openwall.net (193.110.157.125)
  by inbox.vuxu.org with ESMTPUTF8; 7 Jul 2023 15:06:33 -0000
Received: (qmail 17558 invoked by uid 550); 7 Jul 2023 15:06:30 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 17518 invoked from network); 7 Jul 2023 15:06:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=x.fripost.org; h=
	in-reply-to:content-disposition:content-type:content-type
	:mime-version:references:message-id:subject:subject:from:from
	:date:date; s=9df9cdc7e101629b5003b587945afa70; t=1688742378; x=
	1690556779; bh=2E+rtRx5CvG4bQqbVyEyN/XdvmKS/VN2DQbKCcNj+rQ=; b=O
	fd4z05besdHfj2FI8WLusT7VnSQn2uQhzAFhoIwkrAdOmtnaaxy9DVcGn+APQ9bf
	ufYnWooimDYhWPrwBLdliKJu1c/aVhTUruLOfy4nquCpFSR86aHMnOoZMUe7lT8y
	0Vu1j8KW/q9c5HHfQwuV/92lZL3kInWOMlJ8kt0pxUep1PF/qEN9yGx7nGhzWanU
	D0sYnUdRhlviGMtcLaEP+eRQiSbmgacvIisnzQEeeU3LLH9BNmR79OKzVzeMWTSn
	uinM301lynRq58Ty1iozdimxAA28A0IWgBceduVlfHbS8SfxL29NK0zwG54kfxV4
	ysf07t4KCGPszrXdND1Yg==
X-Virus-Scanned: Debian amavisd-new at fripost.org
Date: Fri, 7 Jul 2023 17:05:59 +0200
From: i262jq@0w.se
To: musl@lists.openwall.com
Message-ID: <ZKgp17c9A/u9Ml0K@localhost>
References: <309EDCC9-2402-46B5-BDBD-B96677E470DD@apple.com>
 <20230707124722.GE4163@brightrain.aerifal.cx>
 <054B1907-817E-496D-9F83-7FBE7AB0111A@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <054B1907-817E-496D-9F83-7FBE7AB0111A@apple.com>
Subject: Re: [musl] __MUSL__ macro

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