On 2023-07-24 17:34, Bruno Haible wrote:
Paul Eggert wrote:
It gets this info from mbrtoc32, which on most platforms gets this info
from mbrtowc. This multibyte scanner knows when the bytes it has seen
so far constitute
- a complete character, or
- an invalid character, or
- an incom
Since fnmatch() relies on character classes, and I saw a test failure of
c32_apply_type_test on mingw, it's time to add unit tests for these
character class functions.
2023-07-25 Bruno Haible
iswctype: Add tests.
* tests/test-iswctype.c: New file, based on
tests/test-c
It is useful to disable debug assertions when benchmarking.
But not for the entire tests/ directory, of course — we want to know about
assertion failures in the unit tests.
This patch is not perfect, but good enough for the mb*iterf benchmarks.
2023-07-25 Bruno Haible
Compile benchma
This patch makes gnulib's and libunistring's UTF-8 decoder (mainly
u8_mbtouc) more Unicode Standard compliant, regarding
https://www.unicode.org/versions/Unicode15.0.0/ch03.pdf section 3.9.
2023-07-25 Bruno Haible
unistr/u8-*: Make Unicode decoder more Unicode Standard compliant.
On 24/07/23 21:46, Bruno Haible wrote:
> This patch fixes the remaining problems of fnmatch() on Cygwin,
> native Windows, and AIX in 32-bit mode.
>
> I think the code changes are in glibc style, because
> - they use upper-case names for macros,
> - the macro names are aligned to the type a
