From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6757 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: the case for __MUSL__ Date: Mon, 29 Dec 2014 12:37:13 -0500 Message-ID: <20141229173713.GM4574@brightrain.aerifal.cx> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1419874656 9583 80.91.229.3 (29 Dec 2014 17:37:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Dec 2014 17:37:36 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6770-gllmg-musl=m.gmane.org@lists.openwall.com Mon Dec 29 18:37:29 2014 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Y5eG0-000866-SB for gllmg-musl@m.gmane.org; Mon, 29 Dec 2014 18:37:29 +0100 Original-Received: (qmail 23874 invoked by uid 550); 29 Dec 2014 17:37:27 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 23866 invoked from network); 29 Dec 2014 17:37:26 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:6757 Archived-At: On Mon, Dec 29, 2014 at 11:17:55AM -0600, Josiah Worcester wrote: > On Dec 29, 2014 11:15 AM, "Josiah Worcester" wrote: > > I suspect the thing to do here is more to iterate over the set of chars > and construct the table as needed: there's no sensible interface to this > bit of functionality in a standard way (and musl to my knowledge doesn't > have the table you want exposed anywhere). Note that doing it that way > ought to just work anywhere. > > Minor correction: the table is exposed via __ctype_b_loc which you were > using. :) This is not a public interface for musl. The macros needed to interpret the table are not in any public headers, and the table contents cannot change in any locale-specific manner. The only purpose of these tables is for ABI compatibility with glibc-linked binaries. When building against musl, applications should ue the portable standard ctype.h functions/macros (and the portable table building approach you suggested if they need tables) rather than hacking in access to the ABI-compat tables. Future versions of musl may have an option for omitting all glibc ABI-compat bloat for users not needing it. Rich