DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 65B5A3858C66
To: cygwin@cygwin.com
Subject: Re: character class "alpha"
Date: Mon, 31 Jul 2023 20:43:21 +0200
Message-ID: <4474610.kIfH5X4irW@nimes>
In-Reply-To: <ZMf7aqxU8awRQM4v@calimero.vinschen.de>
References: <3884636.3uDm00564X@nimes> <ZMfzbOOJth8Mk+rJ@calimero.vinschen.de>
 <ZMf7aqxU8awRQM4v@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="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

Corinna Vinschen wrote:
> there are more of those expressions which are disabled on glibc and
> fail on Cygwin, for instance in test-c32iscntrl.c.  Maybe it's actually
> the better idea to disable them on Cygwin, too, rather than to change
> a working system...

Sure. There is no standard how to map the Unicode properties to POSIX
character classes. Other than the mentioned ISO C constraints for
'digit' and 'xdigit' and a few POSIX constraints, you are free to
map them as you like. For glibc and gnulib, I mapped them in a way
that seemed to make most sense for applications. But different
people might come to different meanings of "make sense".

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