Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Kaz Kylheku <433-929-6894@kylheku.com>
Newsgroups: comp.lang.c
Subject: Re: Word For Today: =?UTF-8?Q?=E2=80=9CUglification=E2=80=9D?=
Date: Wed, 13 Mar 2024 22:10:04 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <20240313150115.10@kylheku.com>
References: <uso6or$3t3jn$3@dont-email.me> <usopec$4eob$1@dont-email.me>
 <usort1$4t2r$1@dont-email.me> <usptlp$c79g$1@dont-email.me>
 <usqhjg$gpvk$2@dont-email.me> <usrl1b$r66p$1@dont-email.me>
 <ust76r$15mv5$4@dont-email.me>
Injection-Date: Wed, 13 Mar 2024 22:10:04 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="1e487003ba0b33508276944d7fda6b3a";
	logging-data="1241239"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/2L9/nofzLrPY9Lh+oNx3yUpi9uPFtb6Y="
User-Agent: slrn/pre1.0.4-9 (Linux)
Cancel-Lock: sha1:v+oNJUsioGU5WxvRg+YE0isZiog=
Bytes: 2349

On 2024-03-13, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> On Wed, 13 Mar 2024 03:36:11 -0400, James Kuyper wrote:
>
>> Yes, I do, and so do implementors. Avoiding those clashes is their
>> responsibility.
>
> Implementors of the C standard? What about providers of other libraries?

One possible point of view is that the integrators who put together a
GNU/Linux distro effectively take on the role of C implementors.

If a clash takes place among any libraries in Debian or Alpine or GNU
Guix or what have you, you can regard that as a bug in the distro. The
distro can fix it however they see fit: apply a local patch to one or
more libraries, and get possibly get that upstreamed, or not.

(It makes sense to get that upstreamed, because other distros are all
building most of the same libraries; a clash between libraries can
affect any distro the same way as any other.)

In any case, the C standard doesn't distinguish any party other than
implementor and user. Libraries that are not in the implementation are
in the program being presented for translation and linkage, and
clashes in the program are the program's problem.

-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca