Hi,
Bernhard Voelker <m...@bernhard-voelker.de> writes:
> There's been some char-related changes in the related gnulib files between
> findutils 4.9.0 (2022) and the new 4.10.0.
> Would you please test if that problem still exists there?
No harm in trying this. However, I feel like this might be a platform
bug. Yuqi can you please tell me what operating system / libc
implementation you encountered this on?
As far as the behavior goes, the test is correct. From POSIX
Issue 7 [1]:
The members of the structure with type char * are pointers to
strings, any of which (except decimal_point) can point to "", to
indicate that the value is not available in the current locale or is
of zero length. The members with type char are non-negative numbers,
any of which can be {CHAR_MAX} to indicate that the value is not
available in the current locale.
Collin
[1] https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/
