[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4d746cc3-5f72-869c-afcb-245f002dfd68@mirbsd.de>
Date: Fri, 11 Jul 2025 20:55:39 +0200 (CEST)
From: Thorsten Glaser <tg@...bsd.de>
To: musl@...ts.openwall.com
cc: "A. Wilcox" <AWilcox@...cox-Tech.com>
Subject: Re: [PATCH v1] string.h: Unconditionally expose C23
functions
On Fri, 11 Jul 2025, Rich Felker wrote:
>However in this case, the namespace str* and mem* was already reserved,
>so I think even without that policy, there's no reason not to expose
>them unconditionally unless we're using strictness to expose
>non-conforming application-side expectations.
Given there seems to be *no* tool in existence that can take a
C codebase and check it for use of reserved identifiers, like
is + lowercase, that is, no accessible way for people to avoid
accidentally using “reserved” identifiers, I’d ask to at least
consider it a little longer given you have actual user reports
that they have to patch out things like this downstream.
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
