From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6332 Path: news.gmane.org!not-for-mail From: Sergey Dmitrouk Newsgroups: gmane.linux.lib.musl.general Subject: Re: Constants to decode __ctype_b_loc() table Date: Wed, 15 Oct 2014 22:19:46 +0300 Message-ID: <20141015191946.GB1552@zx-spectrum.accesssoftek.com> References: <20141015104142.GA2186@zx-spectrum.accesssoftek.com> <20141015113207.GF4874@port70.net> <20141015120531.GA5017@zx-spectrum.accesssoftek.com> <20141015165136.GS32028@brightrain.aerifal.cx> 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 1413400820 15490 80.91.229.3 (15 Oct 2014 19:20:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2014 19:20:20 +0000 (UTC) To: "musl@lists.openwall.com" Original-X-From: musl-return-6345-gllmg-musl=m.gmane.org@lists.openwall.com Wed Oct 15 21:20:13 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XeU7C-0004gz-KG for gllmg-musl@plane.gmane.org; Wed, 15 Oct 2014 21:20:06 +0200 Original-Received: (qmail 13349 invoked by uid 550); 15 Oct 2014 19:20:05 -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 13341 invoked from network); 15 Oct 2014 19:20:04 -0000 Content-Disposition: inline In-Reply-To: <20141015165136.GS32028@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:6332 Archived-At: On Wed, Oct 15, 2014 at 09:51:36AM -0700, Rich Felker wrote: > Basically, libstdc++ should be using ... Well, I'm talking about libc++, not libstdc++. libc++ doesn't have such headers and all is kept in one big locale.cpp. It's easy to hard-wire these constants for generic case, but is it really correct solution? It doesn't seem to be standardized. Values in os/generic/ctype_base.h differ from those one can find in C++ standard. There is even a comment: // Default information, may not be appropriate for specific host. My point is that musl can have these masks defined to arbitrary values and there is currently no way for a client to know exact values. It just happens to work, no guarantees. The question is whether you want to keep it in this somewhat incomplete state, when particular values of constants are assumed and undocumented (e.g. if this is really just for libstdc++, which can live without constants). Regards, Sergey