[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141015113207.GF4874@port70.net>
Date: Wed, 15 Oct 2014 13:32:07 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: Constants to decode __ctype_b_loc() table
* Sergey Dmitrouk <sdmitrouk@...esssoftek.com> [2014-10-15 13:41:42 +0300]:
>
> musl provides symbols for the following functions:
>
> - __ctype_b_loc
> - __ctype_tolower_loc
> - __ctype_toupper_loc
>
these are nonsense abi
required for ctype_base::mask feature of c++
so used by libstdc++ and libc++
> The last two of them return values that do not need special
> interpretation. The first one returns value pointing to a table of
> bitmasks, but I'm unable to find where musl defines meaning of the bits.
> Values seem to be compatible to the ones defined by glibc though.
>
iirc the meaning of the bits are defined in the c++ standard
either that or glibc <-> libstdc++ abi convention
> Is this intentional (some kind of compatibility with other libc
> implementation) or definition of _IS... macros is just missing and
> you'd accept a patch to add them?
i think glibc uses them for is* macros internally
but musl doesnt
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.
