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.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 10748 invoked from network); 5 Jan 2021 10:54:33 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 5 Jan 2021 10:54:33 -0000 Received: (qmail 9890 invoked by uid 550); 5 Jan 2021 10:54:26 -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 9871 invoked from network); 5 Jan 2021 10:54:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1609844054; bh=CIE+qy0MxOZ2TGP5cq1RGdG0BeV2TIsKW9dtOFGIZ1k=; h=X-UI-Sender-Class:Date:From:To:Subject:References:In-Reply-To; b=jQQjydDHlX4SADGYktJuuH/oTIlBnMgUPx3ZoXnpXLsjgyXYK/jra5yshGjH5HLis ng6iGM9COW0c6K72hLn6YgS2v2Q3tAdkxuNPRaK22nfmhmrq+VCKIAOFoJSUo44CyI 0R5P4y8nZGNWNTVadSBDV4cYs7q4N5GjF5p0Mdbk= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Date: Tue, 5 Jan 2021 11:54:14 +0100 From: Markus Wichmann To: musl@lists.openwall.com Message-ID: <20210105105414.GA2006@voyager> References: <20210105014834.13622-1-ericonr@disroot.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20210105014834.13622-1-ericonr@disroot.org> User-Agent: Mutt/1.9.4 (2018-02-28) X-Provags-ID: V03:K1:zwvLiSwPXWumWY32Tp3cYqEWKKhqlq+rlRsuKssVgZJesBujWxW EWjKZs14JTmzR8wQASFB+045IFGGy9Il8G8G8CUtpn1v+Fu+s37FYXRkyr44NEynJ8CGfdI uTeEW+foCBfrTeOBFQQBu9ILjfOl0Z/8Op5fLoPFM7c7iWbo/P+EUvNLzreWdSqBy50sAn3 zEuF5cep7Ax7GHsqubgaw== X-UI-Out-Filterresults: notjunk:1;V03:K0:pO2TxEAc+ro=:VakiF560eXoCyWRVyo4zge LfRG/rBpi/tDMKCdWXKn3VdUbN63v5P9BdKBXvpBSq0pwBzzuvvWixGoMXwmhvcFl24/wRJ4g AfavqA2gVdgTbDcty+pDglC76km3Qvu/MYCsZIcwku8kiK7IgTVdJu+fz8Nftk7CQOH0Os5BL 0sIuvowyKoxohy52NpIWf6Mmbfy6CgnOh744SzqXCEKo2CQSsOeT1D+mRpJg1uhKdwcEvLnPN JCn9qC9YTNtWK9ofq9bBgswSuCaNGpVA8wOZ+7vaA/sfOOOCnbn0gpafk+1W2EXcTCnR8R/Da xhr2MDBFSv3x4ZVvwz7kzVMNnq7rTTTAos3AlZL5rjcURtMGaHg7NiAhEZxQlDSgovIvVKXZL wqrORqXicQrMgNlkViwrcjrNGzlvZ+y2EmMwzZFeuCgYsFaUVAo/tKGVnuQiVwmSqTGMVsvWX +JzIrvBgDEPWGnUd73XCQTjdy4z2REnsRT8Sxc0Ra8H6mBX4FIseVLlIdewaRv6tNdl9vtpzL XZazMX8pGg8eEhmz4x1Rbwf6X0wa+OdVXAilVmI+RIefhTPX+1bvT8wLCoiMvESCBJ3rSNY8h D4DGJboO3MH9UjBlxf++80djnT0e4lXiGaSZ7sUH3Xfw5cmSv9VknfKQHQ9A3akYefxfHWeim 01p7sE1sU2d3Jhn6lLqii8AGbDda4WHVYSi+JdRnWLWOb5PkF4XDqOdYFuBmvZgVz6jD9+ozl c2cvqMO1lBuF5pgmc8uoS+bkxcsTOq82WW7pQ5F5hTmmhQ8YQoBIsKO20RoOktvKdcbrGiBxZ EllliVk9J9blVAlHdX5TFnGXjIOiiO6fuJ6THWDi5ibquoG9xy6DecbHTytpMqXOm661Dzqv6 9dMC3tHxhDTPpPcPXSJA== Subject: Re: [musl] [PATCH] guard isascii() macro when using C++ On Mon, Jan 04, 2021 at 10:48:34PM -0300, =C9rico Nogueira wrote: > From: =C9rico Rolim > > otherwise one can get compilation errors in C++ code that uses isascii > as an identifier > Well, this is a namespacing issue. The identifier in contention here is only exposed if defines are set identifying the source file as POSIX code. POSIX specifies the isascii macro, though it marks it as obsolete. However, it means that no-one, C or C++, can use isascii as identifier when including ctype.h if they declare POSIX compatibility. So one of those three things has to go: Either the source files in question must avoid including ctype.h, or they must avoid using the isascii identifier, or they must avoid declaring POSIX compatibility. In all cases, this is not a C vs. C++ issue, only a namespacing issue. And not wrong in the library, but in the application. Ciao, Markus