On 7/11/24 17:50, Eric Blake wrote:
In contrast, it's not OK to call memchr ("", 0, SIZE_MAX).
...this claim appears to be unsupported. Both C23 and POSIX 2024
state that memchr() "...shall behave as if it reads the characters
sequentially and stops as soon as a matching character is found",
On Sat, Jul 6, 2024 at 12:40 PM Bruno Haible wrote:
>
> Paul Eggert wrote:
> > > are we OK to drop the ability to run gnulib-tool on Solaris 10?
> >
> > I'm OK with it. When I deal with Solaris 10 (hey, our department's admin
> > server is still Solaris 10 sparc!) I run gnulib-tool elsewhere and c
YX Hao wrote:
> > `c32*.c` files are newly included, but `uc_is_*` functions are not
> The 2nd error also has gone with a newer gnulib commit 92cdf62b,
> which is merged from the head of wget, using a hack of:
> ```
> sed -i "s/!_GL_SMALL_WCHAR_T/defined _GL_SMALL_WCHAR_T/" lib/fnmatch.c
This work
On Wed, Jun 26, 2024 at 05:33:55PM GMT, Paul Eggert wrote:
> On 6/26/24 07:57, Bruno Haible wrote:
> > Po Lu wrote:
> > > I believe that the semantics of the POSIX specification of this GNU
> > > function omit the implied guarantee that strnlen will never examine
> > > bytes beyond the first null b
