Re: From wchar_t to char32_t, new module mbszero

2023-07-19 Thread Bruno Haible
Paul Eggert wrote: > > On NetBSD, I apparently did not locate the right source code of the mbsinit > > function, due to the complexity of the citrus code. And did not want to > > debug > > it, because debugging in libc code without debugging information is often > > a waste of time. > > I looked

Re: From wchar_t to char32_t, new module mbszero

2023-07-18 Thread Paul Eggert
On 2023-07-17 09:53, Bruno Haible wrote: On NetBSD, I apparently did not locate the right source code of the mbsinit function, due to the complexity of the citrus code. And did not want to debug it, because debugging in libc code without debugging information is often a waste of time. I looked

Re: From wchar_t to char32_t, new module mbszero

2023-07-17 Thread Bruno Haible
Running the test suite on Minix shows test failures. There, like on NetBSD, the source code investigation was incomplete. This patch fixes the failures. 2023-07-17 Bruno Haible mbszero: Fix for Minix. * lib/wchar.in.h: (_GL_MBSTATE_INIT_SIZE): Don't define on Minix. (_

Re: From wchar_t to char32_t, new module mbszero

2023-07-17 Thread Bruno Haible
Paul Eggert wrote: > > However, after implementing mbszero with this data and enabling its use > > in many places, I got test failures on NetBSD and Solaris. > >- On NetBSD, the minimum we need to clear is 28 bytes. > >- On Solaris OmniOS and OpenIndiana, the minimum we need to clear is 16

Re: From wchar_t to char32_t, new module mbszero

2023-07-16 Thread Paul Eggert
On 2023-07-16 01:43, Bruno Haible wrote: Paul Eggert wrote: However, after implementing mbszero with this data and enabling its use in many places, I got test failures on NetBSD and Solaris. - On NetBSD, the minimum we need to clear is 28 bytes. - On Solaris OmniOS and OpenIndiana, the m

Re: From wchar_t to char32_t, new module mbszero

2023-07-16 Thread Bruno Haible
Paul Eggert wrote: > > By reading the source code of FreeBSD, NetBSD, OpenBSD, macOS, Solaris, > > and so on, I can easily determine > >- which parts of the mbstate_t mbsinit() tests, > >- which parts of the mbstate_t the various functions use. > > But in order to understand what interdepen