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=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 32330 invoked from network); 23 Sep 2022 14:59:03 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 23 Sep 2022 14:59:03 -0000 Received: (qmail 19958 invoked by uid 550); 23 Sep 2022 14:59:00 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 19923 invoked from network); 23 Sep 2022 14:58:59 -0000 Date: Fri, 23 Sep 2022 10:58:44 -0400 From: Rich Felker To: =?utf-8?B?SuKCkeKCmeKCmw==?= Gustedt Cc: musl@lists.openwall.com Message-ID: <20220923145843.GZ9709@brightrain.aerifal.cx> References: <20220923162518.56284329@inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220923162518.56284329@inria.fr> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] C23 implications for C libraries On Fri, Sep 23, 2022 at 04:25:18PM +0200, Jā‚‘ā‚™ā‚› Gustedt wrote: > Hello, > I have started to compile a document that tries to collect everything > a C library needs for C23 compliance: > > https://htmlpreview.github.io/?https://icube-forge.unistra.fr/icps/c23-library/-/raw/main/README.html > > This is by far not complete and I will try to fill the holes in the > next weeks. Let me know if you have any particular > questions/remarks/additions. Thanks for putting this together. For the most part these look tractable. One small note on wording: your usage of FTM differs from the one we're used to and that's in POSIX, where FTMs are macros the application defines to request some functionality or compliance profile from the implementation, not macros the implementation uses to advertise features to the application. One cute observation: now that headers define macros for their versions, can we just replace the multiple-inclusion test macros with these? I think so. Rich