DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 51HAoTun2888059
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 112FD3858D35
To: cygwin@cygwin.com
Subject: Re: bug in strcasecmp and strncasecmp
Date: Mon, 17 Feb 2025 11:49:50 +0100
Message-ID: <6261974.2l3rmUXbR5@nimes>
Organization: GNU
In-Reply-To: <Z7MIvRl6XKQ0Ky0m@calimero.vinschen.de>
References: <2031387.2IRrRt1zHL@nimes> <Z7MIvRl6XKQ0Ky0m@calimero.vinschen.de>
MIME-Version: 1.0
Precedence: list
From: Bruno Haible via Cygwin <cygwin@cygwin.com>
Reply-To: Bruno Haible <bruno@clisp.org>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

Corinna Vinschen wrote:
> Adding a cast fixes that and I just pushed a matching patch.

Thanks.

> I'm just not sure if that's sufficient in the light of POSIX.1-2024.
> The above expression seems to indicate that strcasecmp and friends are
> now expected to work on multibyte codesets like UTF-8.

They can't work on multibyte strings. This is evident from the fact that
strncasecmp gets one integer as argument, not two integers. In a Turkish
locale, for example, "i" (1 byte) and "İ" (2 bytes) are the same modulo
case.

I agree that the POSIX language is murky because "character" there is
equivalent to "byte", and yet the same page talks about characters and bytes...

For multibyte strings, one needs other functions. See
https://www.gnu.org/software/gnulib/manual/html_node/Comparison-of-string-APIs.html

Bruno


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple