Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104334
MIME-Version: 1.0
References: <CACDmYydDVajyUF3LsFJ4Y7C83LUj4=zb_Pij83TN27UX7oCw-Q@mail.gmail.com>
 <a43d865a-9ff1-84da-a8bc-9482222a3656@gmail.com>
In-Reply-To: <a43d865a-9ff1-84da-a8bc-9482222a3656@gmail.com>
Date: Sun, 10 Feb 2019 22:59:12 +0100
Message-ID: <CACDmYyf8uwiwnAkmSDkJyL6uQEcFgyJGN=aZ=BCwmtLOHPxgAQ@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000034fc770581914e93"
Subject: Re: [PHP-DEV] reasonability of change the mbfl library
From: legale.legale@gmail.com (Legale Legage)

--00000000000034fc770581914e93
Content-Type: text/plain; charset="UTF-8"

Good idea, thanks. should be a bit slower than lookup table, but faster
then now.

On Sun, Feb 10, 2019, 21:02 Rowan Collins <rowan.collins@gmail.com wrote:

> On 10/02/2019 12:29, Legale Legage wrote:
> > This conception can be used for the utf-16 encoding, but table size
> > would be 65536 bytes against 256 byte for the utf-8 table.
>
> Rather than two 65 kilobyte lookup tables with most entries identical,
> would it be reasonable to use a bit mask to check for the range we care
> about?
>
> I may have this slightly wrong, but something like:
>
> #define UTF16_LE_CODE_UNIT_IS_HIGH_SURROGATE (code_unit & 0xFC00 == 0xD800)
> #define UTF16_BE_CODE_UNIT_IS_HIGH_SURROGATE (code_unit & 0x00FC == 0x00D8)
>
> m = UTF16_LE_CODE_UNIT_IS_HIGH_SURROGATE(*(uint16_t *)p) ? 4 : 2;
>
> Regards,
>
> --
> Rowan Collins
> [IMSoP]
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--00000000000034fc770581914e93--